Jump to content

Kelsenellenelvian

Members
  • Posts

    3,115
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Kelsenellenelvian

  1. No because it couldn't be told about here.
  2. Mawwawawawawawawawawawahahahahha After some maniacal testing and a ton of downloads I have the solution... Here is the first and smallest set of 7z files that I could get to extract an iso. Commandline used 7z.exe x Neptune.iso <-- Will extract to the iso dir. There are switches for dest and all that crap too The size of the files compressed is only 213 kb I have included the help file... 7z Files.7z
  3. Yeah after some quick testing you would need 7za AND 7z.dll which would be 1.31megs even compressed.
  4. The one I have in WPI... (I had to 7z it just to upload it. Dang forum and the .exe rule)
  5. Just an idea.... 7z has freely redistributable cmdline extractors. Add one in.
  6. In the uber pack there is reshack w\fx pack and it is linked to in the send to and utilities menus.
  7. Please stop with the excessive use of font modification it doesn't get any extra attention other than just annoying the hell out of us! See forum rule #10: 10. Do not use CAPITALIZATIONS in the topic title or when participating in threads because they will not attract attention - instead it will annoy many of WinCert's members. Using unnecessary font formatting (i.e., bold font, increased font sizes, colored fonts, etc.) on the full body of posts is also discouraged.
  8. The reasoning behind this is the way the integrators handles the entries files. When they are extracted usually all of the crap (i.e. files in the cabs) are dumped into 1 folder and then read. When the entries files ara ALL NAMED THE same they get overwritten and sh!t gets missed...
  9. I really don't think that is possible.
  10. I discontinued the XP x64 UberPacK in favor of keeping just this one. (The contents were nearly the same) For 64bit systemms this (v2.8) is the one you want. The 4.2 is for 32bit.
  11. Lets get a bit technicall here: The component "Removal" in the Toolkit is not "removal" as you think. It is actually "Disable\Enable" Thus it will result in a smaller footprint Post-install, but not on disk.
  12. OK let me clarify a bit more... Things USED to be that after you selected the 2 wims and if you did not change names the toolkit would automagically add x86 or x64 to the end of the name. This no longer happens. The xml I provided in the first post was one I manually and painstakingly made myself. if you look at one made by the toolkit you see this: <NAME>Windows 7 HOMEBASIC x86</NAME> <DESCRIPTION>Windows 7 HOMEBASIC</DESCRIPTION> <FLAGS>HomeBasic</FLAGS> <HARDLINKBYTES>3069177344</HARDLINKBYTES> <DISPLAYNAME>Windows 7 Home Basic</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 7 Home Basic</DISPLAYDESCRIPTION> Note dislplay name was not changed like it used to be.
  13. Here are issues I found with the a-i-o creator: It no longer auto renames images. i.e adding a "86" or a "64" at the end. When editing a description is no longer shows the edited name during the intital install process. (I am attaching a xml for what I thought it did) When editing name and description and canceling it throws a " '' name already exists error"
  14. TECHNICALLY Thats "Reverse Integration" NOT "Slipstreaming", which is what the OP was asking for. :aggressive: :owned: :giveheart:
  15. No sorry ric, it's the krnl files (there's 4 of them) He seems to have tried to change to location of the progress bar. That is EXTREMLY difficult to do and not recommended. I know of a way to fix it and do it properly but I need to know what he has done so far...
×
×
  • Create New...