[T D]

It is quicker from a hdd because transfer speeds are faster.
Look at it like this: you want to run a game, you'd be more likely to make an iso and mount it via Alcohol or Daemon Tools wouldn't you? That's because it#s faster.
But it seems broken if you nlite it.

[Doctor Trout]

T D, on Jul 2 2006, 10:12 AM, said:

It is quicker from a hdd because transfer speeds are faster.
Look at it like this: you want to run a game, you'd be more likely to make an iso and mount it via Alcohol or Daemon Tools wouldn't you? That's because it#s faster.

Oh yeah, I always knew it would be quicker for that very reason, but I was just wondering how much quicker.

T D, on Jul 2 2006, 10:12 AM, said:

But it seems broken if you nlite it.

Are you saying that you can't do it from the hard drive if you nLite it? Is that with the floppy disk trick, or with the boot.ini trick?

[Camarade_Tux]

It may be much faster or not.
It takes me less than 1 minute to start the windows installation and then it needs 2 or 3 minutes to copy files. My installation CD is really small and I have no RAID driver to load.
Still, when I use a virtual machine, where files are read from the hard drive, it only takes 10 seconds to start windows installation and file copy needs 1 minute.

If you have a big CD and RAID drivers to load during textmode part of the setup, then installing from a hard-drive will be much faster. Not because of transfer rates but because of access times.

This post has been edited by Camarade_Tux: 02 July 2006 - 07:15 AM

[T D]

@Doctor Trout: w/the floppy disk trick, I tried it after someone posted about it here.

[Sandro]

i've tried following methods, but none succeeded.

1. ISO Emu Loader, which can load an iso-image by starting up.

2. the methode of loading WinPE-ISO-Image with ramdisk, using setupldr.bin and ramdisk.sys from win2k3 server sp1.

3. boot computer using WinPE, then load WinLite.iso using VCdControlTool.exe of MS, then run setup.exe

4. boot computer using WinPE, and install windows using winnt32.exe in I386,
winnt32 /makelocalsource /noreboot

5. boot computer using dos bootdisk, run smartdrv.exe and run winnt.exe in I386
winnt /s:c:\i386 /u:c:\i386\winnt.sif

6. use the bootsect.dat file, which is created by winnt.exe, copy bootsect.dat into I386, then add an entry into boot.ini
C:\I386\BOOTSECT.DAT="nLite Windows XP SP2 Setup"

7. at first install windows in VMware using WinLite.iso, after the file-copying stage (txtsetup install stage), copy all the files to primary partition of host os, add an entry into boot.ini
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="nLite Windows XP SP2 Setup" /NOEXECUTE=OPTIN /FASTDETECT

8. completely install windows in VMware using WinLite.iso, delete hardware drivers, change computer into Standard PC, then use setupmgr.exe in deploy.cab of windows setup CD to create an unattended answer file, then use sysprep.exe to reseal the system. At last use ghost to copy the VMware Harddisk Image to real Harddisk.

Is installing WinLite.iso using ISO-image file really impossible?

[T D]

Your boot.ini Sandro is messed up. That's the boot execution for a normal Windows OS but instead of "Windows Xp Professional/Home", it's "nLite Windows XP SP2 Setup". Try
multi(0)disk(0)rdisk(0)partition(1)\XPCD\WINNT.EXE="nLite Windows XP SP2 Setup"

This post has been edited by T D: 04 July 2006 - 03:30 PM

[jaclaz]

T D said:

Your boot.ini Sandro is messed up. That's the boot execution for a normal Windows OS but instead of "Windows Xp Professional/Home", it's "nLite Windows XP SP2 Setup". Try
multi(0)disk(0)rdisk(0)partition(1)\XPCD\WINNT.EXE="nLite Windows XP SP2 Setup"

You are telling NTLDR to directly load a DOS 16 bit program?

Entries in boot.ini can only be:
1) An arcpath leading to a directory
2) A bootsector

Some more info and links:
http://www.911cd.net...showtopic=17538

jaclaz

[T D]

I'm guessing I've seen it used to launch a program before w/a direct program entry on a windows upgrade install.