Jump to content

dunk

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About dunk

dunk's Achievements

0

Reputation

  1. dunk

    wim image recompresson

    i used imagex under xp but i cant work out how to recompress - microsoft site says there is a /compress parameter but under xp it doesnt seem to do anything. i can mount and unmount images without any problems but am stuck after that
  2. what tool does vlite use to recompress the image? and does anyone know of a tool that i can recompress a .wim image with i am trying to vlite a multi-version dvd, but after vliting it the dvd contents are larger than 4.5gig. if i use the current vlite rebuild, i only get to keep 1 version in the .wim file
  3. i did some more testing here: it only goes wrong if you are doing an upgrade install without using a winnt.sif without a winnt.sif file, your hacked setup.ex_ doesnt seem to rename itself or load setuporg.exe, it tries to load itself i used pyrons setup.ex_ and added the commands at the end of presetup.cmd to delete any exisiting setup1.exe, then rename setup to setup1 and rename setuporg to setup this works, but it requires manually changing setup.ex_ and presetup.cmd after installing your addon packs. what is the difference between your setup.ex_ and the pyron one? yours automatically runs the setuporg.exe? or renames the existing files?
  4. i am trying to build an install disk with unattended and normal install versions. i have edited a copy of the boot sector and have a second one loading an edited setupld1.bin which looks for a winn1.sif instead. this way i only have one install folder on the disk, with 2 boot loaders, 2 setupldr.bin files and 1 x winn1.sif file with all the i386 folders etc in the normal place. the standard boot file and setupldr.bin doesnt find a winnt.sif so starts a normal install problem is that without the winnt.sif, the bashrat setup starts after the first reboot and i get an error message: "fake setup call himself instead original "setup.exe" setup abort!" the unattended bit works fine as expected the only difference here is the absence of a winnt.sif file - if i replace it then i get a normal working unattended setup. any ideas or is there a better way to integrate the drivers, particularly the txtmode scsi/raid drivers into a normal install, or another way of going about the whole thing.
×
×
  • Create New...