htc

3 monthes ago(Feb. 2005) I've already integrated all the new driver for ASUS A8N-SLI Deluxe mainboard witch has nForce 4 chipset and nForce 4 SLI gfx driver (6800/6600), also with Sil3114r RAID-5 SATA controller as textmode + PnP driver. This was on a multiboot unattended XP SetupCD(Home, Pro and Corp.Ed.) and all slipstreamed with nLite. But inegrate drive with nLite was a bad idea... too many bugs! Instead, I've used the traditional methods: 1) edit txtsetup.sif for textmode drivers and copy .sy_ to i386 2) edit winnt.sif for all the PnP driver pathes 3) put mainboard chipsets drivers in $OEM$/$1/Drivers/1_chip 4) put mass storage drivers in $OEM$/$1/Drivers/2_disk 5) put gfx drivers in $OEM$/$1/Drivers/3_vid and so on... and I've integrated the intel 915/925 chipset drivers for almost one year

Windows XP does the full hardware PnP identification during startup AND detects also new hardware after startup. WinPE/BartPE does only the restrickt PnP hardware identification(mass storage device, HID etc.) and ONLY during startup, so if you want to enable USB stick after booting you have to enable the PnP...

The above mentioned "Flashboot" is in a very primitive form/phase and can only create "single boot" flask sticks. A multiboot option to allow setup diff. Wndows XP/2k/2k3 is not there ... even a single boot to setup win xp in "no emul." mode is also not allowed...So, the possiblity is NOT there!

I think it's time to say "Silence is Gold" - execpt ypu are a IT-Expert of world class and very sure what you say. So you can only post your solution here - for Setup Billboard! "Silence is Gold" !

Have you heard of "Silence is Gold" ? If you not sure, dont statement, just ask! By the way, wellcome in Forum!

It is only a editor for regular windows xp boot screen, not for "setup boot screen" - it is different!

This is dead link.

The answer is not correct. It's only kidding.

I think it's not correct. AFAIK the setup runs at 640x480/8bit(= in 256 coloors). So all the winntbbu.dll posted in the web I've ever seen have the resolution 800x600-1280x1024, this resulted the fact the size of winntbbu.dlls are unneccessary enlarged - though dring the setup only 640x480/8bit displayed! I've made the right one which is only 704000 bytes(uncompressed) in size, as large as the original one(SP2).

why do you all repeate the post of others? One time is enough!

if you dont want to copy all the files to disk, how about just burn it on cd/dvd?

the guide from the "magic iso" site contain nothing about "unattended install" and produce much too large dvd image(waste a lot of space). Every exper of this forum ill advise against such method.

how do you want to install? 1) boot from dos and then install, or 2) boot from PE then install, or 3) boot into a existwindows then install(upgrade/new install)? But it is not the theme of this forum(multiboot setup from cd/dvd)

Bad batch-programming! instead of the bad code echo Now installing Windows 98 SE echo. echo Loading... path=%RAMD%:\;a:\;%CDROM%:\SETUP\98SE\WIN98\ SETUP.EXE /IE /NF echo.you should use the following: echo Now installing Windows 98 SE echo. echo Loading... %CDROM%: CD \SETUP\98SE\WIN98 SETUP.EXE /IE /IS /NF echo.

There are still some settings for burning the cd image file onto cd-r witch may solve the problem, here nero as exaple: If you select the iso image file as source, there are 3 possible burning strategy: 1) TAO 2) DAO 3) DAO96 Principlely the DAO method works with already the most computers, bat sometimes the DAO96(Disk at one with raw data) can help. The TAO works with less PC, but try it harms nothing.

...with my alternative method you will only one $OEM$ folder thus it is very easy to maintain.

No, no, no, no... that's to complicated and a lot of unneccessary work! IT-Expert helps: 1) For each game cd you must create a valid image file(use Alkohol 120% for the copy-protected one, use UltraIso for others). 2) just burn the image files onto DVD. 3) use Alkohol 120% oder DaemonTools to load such image files. 4) if cd change occurs, just load the next image file.

please visit the bartPE forum to find out how to build the driver plugins for bartPE. There are some ready-to-use drviers/utilities for bartPE: http://ubcd4win.com/ With my method(M3) you will achieve almost the same size of M2, but the flexibility of M1, and much faster.

By the way, please do not dobble post!

No, no, no... you are totally on wrong way! Only an IT-Expert can recognize your problem and give you help immediately: Here is the sort answer: If you install windows 9x/ME, you have to load the dos-based cd-rom driver in config.sys and autoexec.bat first! Why? At the first boot time, the mainboard bios of your computer is in "no-emulation" mode and you can access all the files/folders on your CD/DVD without the need to load extra driver for CD/DVD(direct access via mainbaord bios or massstorage controller bios). After that, when you load the windows nt/2k/xp/2k3/linux-boot sectors, the PC keep in "no-emulation" mode but if load dos boot floppy image, the "no-emulation" mode must be terminated and change to "floppy-emulation" mode. At that time you can only access the contents of the floppy image witch was just loaded.

the isolinux/memdisk can load the linux boot floppy disk images, in CD Shell you can direct load the boot sector of linux distribution such as knoppix/knoppicillin...

If you take the "Ultimate Coot CD v3.1(full version)" as an example, you could find there is a mixture of DOS boot floppy images, Linux boot floppy images and a Linux/Knopix distribution on one CD under CD Shell, just take the scripts as examples.

best method for most situation is the "method 3" - named by me. In fact it just a slightly modified method of the traditional way. 1) decompress all oem driver archives provided by the manufacturer, if neccessary 2) recompress the driver, file by file with ms cabmaker/LZX-21 3) grouping the drives, copy to one folder for each group, create sub-groups if there is conflict of filename 4) sort the groups/folders. the resulted folder structure can be seen in following example: under $OEM$\$1\Drivers\ 1_chip\ (put all chipsets drivers in this directory) 2_raid\ (put all scsi/s-ata/raid controller drivers in this directory) 3_vid\ (put all video card drivers in this directory) 4_nic\ (put all network interface card drivers in this directory) 4_nic_wlan\ (put all wireless network card/adapter drivers in this directory) 5_aud\ (put all audio card drivers in this directory) 6_aud_cmi\ (put cmi audio card drivers in this directory, cos name-conflict with realtek/via-ac97 cards) 7_mod_pci\ (put all pci inernal modem drivers in this directory) 7_mod_amr\ (put all amr modem drivers in this directory) 7_mod_usb\ (put all usb modem drivers in this directory) 7_mod_dsl\ (put all usb-dsl, pcmcia-dsl drivers in this directory) 8_media\ (put all multimedia/TV/VCR/Capture drivers in this directory) 9_other \(put all other drivers in this directory) 9_other2\ (put all extrar drivers in this directory) ...... The advantages of this method is: 1) compact und quick: because of the recompression is the size of driver packs very small, and windows setup decompress/copy them to hdd at one stroke in lightning speed, no need for external tools and search for cd/folders. 2) flexible: you can use the drivers also after windows setup, for example for other windows xp witch is already installed(new hardware added, etc) 3) Maintanance friendly: you can add/modify/update the driver at any time, no need for compress the whole archive. A description of such windows xp multiboot unattended setup CD can be seen in my post in this thread: http://www.msfn.org/board/index.php?showtopic=35565

CD Shell v2.1.4 http://www.cdshell.org/files/cds2104.zip

please use a "offline-reader" such as "Teleport" or "Offline Explorer" to capture the crrent pages of the site.