JSe

Thanks TAiN for your quick answer. It would be nice if somebody with access could be so kind to PM me my 9 old posts or the hole threads or give me (temporarly) access to retrieve them by myself. I'm not in hurry about this. Thanks in advance.

Just now I was looking for an old post of me that had been sent to the old driverpacks forum before it had been moved to its own domain. When I see my profile there are 9 posts (or now 10 with this one), but if I search for them nothing is displayed. Has this forum been deleted? Is there still a chance to get an archived version of these posts? Thanks in advance!

[Display] Xresolution = 1920 Yresolution = 1200 BitsPerPel = 32 Vrefresh = 60 These values take effect after the unattended setup has been finished when the system does its first boot. I think that from this point on the monitor works fine, am I right? Bevor this time there is a generic vga driver active working with 640*480 or 800*600 pixels what is not a problem in most cases. One possible cause of your problem could be the Vrefresh frequency beeing "out of range". 75Hz could already be out of range. Please consult the display's manual to find out what resolution it support at which frequencies. The monitor has an analog and a digital input and I would guess your VGA card also has a VGA and a DVI output. A second possible problem with this combination is that both devices are trying to autodetect on which of these two ports the other device is connected. There could be timing problems causing not to find each other respectively lose their connection when the video signal breakes or changes what does happen many times while setup. To diagnose the problem and as a workaround you can try the following things: - connect the display and the VGA card with both, a VGA and a DVI cable - connect the display only with a VGA cable. - switch off the autodetection in the display menu if possible - try the "Autoadjust" function of the display if it exist while the setup is in textmode. Im not sure if this will help but I had the same problem some time ago and the "two cable" did the trick. Now when I install these PCs again I do simply sit out this problem until the first boot after setup.

I didn't try this until now altough I should have. Our own distribution share already existed when I found this project. Our "unattended" began in 1997 with WinNT. So to help solving your problem it would be nice to have some more information. - what machines are these two (especially what chipset and IDE controller do they have?)- at which phase of setup does the blue screen happen and what it's contents? - what's in the [unattended] section of your unattend.txt This limit is 4096 chars. If you use the "standard" BTS collection and you did not change the directory names C:\D\... this limit will not be exceeded.

@meridian67 Is your drive H:\ a network share or a local HD, and if it is a network, what brand is your server?

This is one solution: This may be another: you will have to install two independant systems which are hidden from each other using a boot manager. My preffered configuration for this is the following: |---P1---||---P2---||---P3---||---L1---| P1 Primary Fat16 100MB containing bootmanger (always hidden) P2 Primary NTFS 10GB first XP System (Hidden or C:\) P3 Primary NTFS 10GB second XP System (Hidden or C:\) L1 Logical FAT32 or NTFS XXGB Datadrive (D:\ always visible) So P2 and P3 are the two independant systems where you can install one of them while the other one is kept hidden. As the bootmanger I use GRUB 0.97 (others are possible also here - there are also bootmangers not requiring their own partition - but I have on P1 still a bootable MSDOS to start full automated unattended setup from network). You can convert your existing partition scheme to this one using Partition Magic 8.0, but be carefull: - it can dangerous using such programs (you should have a backup of your HD) - this is comercial software - its not 100% foolproof, but if you have some knowledge about partitions its controllable And this may be a third: Buy a second HD and change it with your existing one for making setup experiments.

You can use it also to prepare a CD-installation. Assume your CD-Root is D:\UWXPCD_ROOT, so you will have to call "drvloop.cmd WINXP D:\UWXPCD_ROOT\$OEM$\$1\OemDrv"This will copy all XP-Drivers from the "well sorted" source to the six subdirs. Your winnt.sif must contain OEMPnPDriversPath="Oemdrv;OemDrv\1;OemDrv\2;OemDrv\3;OemDrv\4;OemDrv\5" what can be handled as a constant that does not change as long the six subdirs are enough to hold all driver files without overwriting files with the same names.

The problem is that in some (non English?) versions the files svcpack.inf and sysoc.inf are in unicode format and not ansi. There has been a discussion in RyanVM's forum See here about this problem and there has also been a download link for a tool named unicode2ansi.exe but this link seems not to be valid any longer. Does anybody still have this file?

I'm the maintainer of an internal driver collection which exists for a long time. It has many similarities with BTS's collection (using M1) and also some differences. So it may be usefull to report here our solution to give some ideas to BTS's collection. Our collection is stored on a network share with the following strcture: .\WinDRV\<category>\<DriverDir>.<Extension>\<Driverfiles and Subdir (if exist)> where <category> is one of Audio, Chipset, Graphic, Modem, Monitor, Net, Other, Proz, Scanner, SCSI <DriverDir> is a more or less descriptive Name of the vendor and the device, for example: SIS900, AdpU320, RTLAC97, ... <Extension> is a string of tree characters where the 1st specifies the usage of the driver for Win2000, the 2nd for WinXP(IA32) and the 3rd is for Win2003(IA32). An example is .00_ what means the driver is usable for Win2000 and WinXP and not for Win2003. <Driverfiles and Subdir> is the same we can find in any directory of BTS's collection. When we started with this collection the limit of OEMPnPDriversPath was 128 characters (Win2000 SP1)! So the solution was and is OEMPnPDriversPath="Oemdrv;OemDrv\1;OemDrv\2;OemDrv\3;OemDrv\4;OemDrv\5" and a *.cmd file that brings the "well sorted" collection in the new structure with only 6 directories. Thier contents is not manageable by a human in any kind, so on every change of the original collection these 6 directories will be deleted an recreated. Theoretical these 6 directories could be reduced to only one, but there are drivers that contain files with the same name but diffrent version. A typical example is a3d.dll what is part of many sound drivers. So the most DriverDirs have a "0" in their extension what means they are to be copied to \OemDrv, if there are double files the extensions is one of "1" to "5" and will be copied to \OemDrv\1 to \OemDrv\5 The cmd that does this work is: @echo off rem DRVLOOP 2004/12/11 JSe rem call with "DRVLOOP OS Destination" rem --- Sicherheitsabfrage ----------------------- rem -- (erstellt von einem gebrannten Kind) ------ if not exist %2\!htwmdrv.txt goto FAIL rem --- delete the destination dir ---------- del %2\*.* /F /S /Q for /D %%D in (%2\*) do rd /S /Q %%D if %1 == WIN2000 ( for /D %%D in (Audio\*.0* Chipset\*.0* Graphic\*.0* Modem\*.0* Monitor\*.0* Net\*.0* Other\*.0* Proz\*.0* Scanner\*.0* SCSI\*.0*) do xcopy %%D\*.* %2\ /S for /D %%D in (Audio\*.1* Chipset\*.1* Graphic\*.1* Modem\*.1* Monitor\*.1* Net\*.1* Other\*.1* Proz\*.1* Scanner\*.1* SCSI\*.1*) do xcopy %%D\*.* %2\1\ /S for /D %%D in (Audio\*.2* Chipset\*.2* Graphic\*.2* Modem\*.2* Monitor\*.2* Net\*.2* Other\*.2* Proz\*.2* Scanner\*.2* SCSI\*.2*) do xcopy %%D\*.* %2\2\ /S for /D %%D in (Audio\*.3* Chipset\*.3* Graphic\*.3* Modem\*.3* Monitor\*.3* Net\*.3* Other\*.3* Proz\*.3* Scanner\*.3* SCSI\*.3*) do xcopy %%D\*.* %2\3\ /S for /D %%D in (Audio\*.4* Chipset\*.4* Graphic\*.4* Modem\*.4* Monitor\*.4* Net\*.4* Other\*.4* Proz\*.4* Scanner\*.4* SCSI\*.4*) do xcopy %%D\*.* %2\4\ /S for /D %%D in (Audio\*.5* Chipset\*.5* Graphic\*.5* Modem\*.5* Monitor\*.5* Net\*.5* Other\*.5* Proz\*.5* Scanner\*.5* SCSI\*.5*) do xcopy %%D\*.* %2\5\ /S ) if %1 == WINXP ( for /D %%D in (Audio\*.?0* Chipset\*.?0* Graphic\*.?0* Modem\*.?0* Monitor\*.?0* Net\*.?0* Other\*.?0* Proz\*.?0* Scanner\*.?0* SCSI\*.?0*) do xcopy %%D\*.* %2\ /S for /D %%D in (Audio\*.?1* Chipset\*.?1* Graphic\*.?1* Modem\*.?1* Monitor\*.?1* Net\*.?1* Other\*.?1* Proz\*.?1* Scanner\*.?1* SCSI\*.?1*) do xcopy %%D\*.* %2\1\ /S for /D %%D in (Audio\*.?2* Chipset\*.?2* Graphic\*.?2* Modem\*.?2* Monitor\*.?2* Net\*.?2* Other\*.?2* Proz\*.?2* Scanner\*.?2* SCSI\*.?2*) do xcopy %%D\*.* %2\2\ /S for /D %%D in (Audio\*.?3* Chipset\*.?3* Graphic\*.?3* Modem\*.?3* Monitor\*.?3* Net\*.?3* Other\*.?3* Proz\*.?3* Scanner\*.?3* SCSI\*.?3*) do xcopy %%D\*.* %2\3\ /S for /D %%D in (Audio\*.?4* Chipset\*.?4* Graphic\*.?4* Modem\*.?4* Monitor\*.?4* Net\*.?4* Other\*.?4* Proz\*.?4* Scanner\*.?4* SCSI\*.?4*) do xcopy %%D\*.* %2\4\ /S for /D %%D in (Audio\*.?5* Chipset\*.?5* Graphic\*.?5* Modem\*.?5* Monitor\*.?5* Net\*.?5* Other\*.?5* Proz\*.?5* Scanner\*.?5* SCSI\*.?5*) do xcopy %%D\*.* %2\5\ /S ) if %1 == WIN2003IA32 ( for /D %%D in (Audio\*.??0* Chipset\*.??0* Graphic\*.??0* Modem\*.??0* Monitor\*.??0* Net\*.??0* Other\*.??0* Proz\*.??0* Scanner\*.??0* SCSI\*.??0*) do xcopy %%D\*.* %2\ /S for /D %%D in (Audio\*.??1* Chipset\*.??1* Graphic\*.??1* Modem\*.??1* Monitor\*.??1* Net\*.??1* Other\*.??1* Proz\*.??1* Scanner\*.??1* SCSI\*.??1*) do xcopy %%D\*.* %2\1\ /S for /D %%D in (Audio\*.??2* Chipset\*.??2* Graphic\*.??2* Modem\*.??2* Monitor\*.??2* Net\*.??2* Other\*.??2* Proz\*.??2* Scanner\*.??2* SCSI\*.??2*) do xcopy %%D\*.* %2\2\ /S for /D %%D in (Audio\*.??3* Chipset\*.??3* Graphic\*.??3* Modem\*.??3* Monitor\*.??3* Net\*.??3* Other\*.??3* Proz\*.??3* Scanner\*.??3* SCSI\*.??3*) do xcopy %%D\*.* %2\3\ /S for /D %%D in (Audio\*.??4* Chipset\*.??4* Graphic\*.??4* Modem\*.??4* Monitor\*.??4* Net\*.??4* Other\*.??4* Proz\*.??4* Scanner\*.??4* SCSI\*.??4*) do xcopy %%D\*.* %2\4\ /S for /D %%D in (Audio\*.??5* Chipset\*.??5* Graphic\*.??5* Modem\*.??5* Monitor\*.??5* Net\*.??5* Other\*.??5* Proz\*.??5* Scanner\*.??5* SCSI\*.??5*) do xcopy %%D\*.* %2\5\ /S ) rem --- Sicherheitsfile kopieren ------------------ echo Sicherheitsdatei > %2\!htwmdrv.txt copy shortify.cmd %2\.. pushd cd %2\.. call shortify.cmd del shortify.cmd popd goto ENDE :FAIL echo. echo Die Sicherheitsdatei !htwmdrv.txt wurde nicht gefunden! echo. pause :ENDE Sorry, there are very long lines and some german words inside, but I hope its understandable. The drvloop.cmd will be called for example by the xp.cmd: @echo off rem XP.cmd rem Kopieren aller relevanten Treiber in ein Verzeichnis rem 2002/07/09 JSe rem 2004/01/28 English.w hinzugefuegt echo copydrv laeuft gerade! > copy-msg.txt echo %username% >> copy-msg.txt call drvloop.cmd WINXP ..\WinXP\deutsch.w\I386\$OEM$\$1\OEMdrv rem call drvloop.cmd WINXP ..\WinXP\english.w\I386\$OEM$\$1\OEMdrv del copy-msg.txt There are some advantages against BTS's collection: - OEMPnPDriversPath is constant and keeps short - drivers that support diffrent Win versions have to be managed only once - the subdirs of some drivers will not be included in OEMPnPDriversPath (what is not necessary) - the concept of the extensions can be advanced to store more usage criteria But there are also some disvantages: - the check for double files is done "by hand" - the categories are "hard coded" - its possible that BTS's collection will need more than 6 directories (its bigger than our's) This post is thought only as a information and for discussion. If somebody finds one of the ideas usefull please feel free to use it.

Sorry, my post was not clear enough. I do not start the unattended setup using Windows 98, I do start it using MSDOS Version 7.10. This is the the MSDOS version underlaying Windows 98 SE.There are many reasons for doing that: 1. I can start with a floppy disk see a good collection of Network Bootdisks 2. A (MS)DOS disk can easy be imaged to boot from CD, from memory stic, from network (PXE, etherboot) and a small hidden partition on PC. 3. I have a distribution share point on network which is highly maintained as installation base for about 1000 PCs. 4. There are scripts and tools to autopartition, write small (most MSDOS) images and autostart unattended setups by reading the MAC-Address from network driver. 5. It has been historically grown, other persons are involved. This "project" began in 1997 with WinNt, at this time booting from a CD was a pain! 6. There are still PC in computer pools that don't have a CD drive. I think "shortify" all names won't break anything, it should also work for all other users of BTS's driver collection. And its highly compatibel to the original Win2K / WinXP CD. Btw. I have my own driver collection which is not as big and some drivers are not as current than in BTS's collection but it exist for a long time. And it contains some other features still missing in this collection. In the next days im going to post some of them in this forum.

Hallo All, BTS's Driverpack is a great piece of work. Thank's for this. But I have found a problem using M1 to integrate it to my share point on network to be used by an unattended installtation starting with winnt.exe from MSDOS 7.10 (WIN98). There are many files in the driver directories and also from the Driverpacks itself: BTS_DPs_finish.cmd SetupCopyOEMInf.exe WatchDriverSigningPolicy.exe that do not conform the 8.3 name convention. These files will only be copied with their short names which makes them unusable if they are needed in GUIMode. But there is a possibility to handle this problem. Its to use the file $$Rename.txt in the $1 directory. As a first solution I have written shortify.cmd file, which has to be startet after RUN_ME.cmd. It searches recursively all subfolders of ...\$oem$\$1 and renames all files with non 8.3 file names to their short 8.3 name and makes an entry with short_nam.dat="Original Long File Name" in the $$Rename.txt file. At the begin of GUIMode at T39 all these files will be renamed back by setup. BTW, setup itself uses $$Rename.txt in Textmode to store all the renaming operations from txtsetup.sif to be executed at the T39 of GUIMode. So far it solved my problem, but I would like to hear if other users had the same problem and if yes, if we should try to integrate the functionality of this *.cmd into RUN_ME.cmd? shorify.cmd: @echo off setlocal ENABLEDELAYEDEXPANSION if %1.==. ( set SHORTIFYPATH= set SHORTIFYFN=%CD%\$$RENAME.TXT set SHORTIFYSELF=%CD%\SHORTIFY.CMD echo Rename-File is !SHORTIFYFN! if exist !SHORTIFYFN! ( del !SHORTIFYFN! ) ) else ( set SHORTIFYPATH=%SHORTIFYPATH%\%1 ) for /D %%I in (*) do ( cd %%I call %SHORTIFYSELF% %%I cd .. ) echo Processing files in %SHORTIFYPATH% set SHORTIFYHDR=NEEDED for %%I in (*) do ( if /I %%~nxI NEQ %%~snxI ( if !SHORTIFYHDR!==NEEDED ( echo. >> %SHORTIFYFN% echo [%SHORTIFYPATH%] >> %SHORTIFYFN% set SHORTIFYHDR= ) ren %%~nxI tempname.dat ren tempname.dat %%~snxI echo %%~snxI="%%~nxI" >> %SHORTIFYFN% ) ) endlocal