robnjay

My apologies, Bashrat... Why did you change the driverpacks to use the "detachedprogram section"? Was there a problem with [GUIRunOnce]? I built a CD tonight and was presented with an error during last boot - Taskkill.exe could not find "framedyn.dll" and failed twice or three times. When the computer booted all the way into Windows, "Rundll32.exe" failed for the same reason, and "srclient.dll" wasn't found. The computer booted up without Internet Explorer (??!!). Also, I attempted to run my "applications.cmd" from the "BTS_DPs_finish.cmd" file: :Cleanup IF EXIST %INSTDIR%\applications.cmd START /WAIT %INSTDIR%\applications.cmd IF EXIST %INSTDIR%\applications.cmd CMD /C RD /S /Q %SystemDrive%\Install "applications.cmd" ran, but I got 7zip errors when it tried to run the Adobe Acrobat 7 installer (?!!) and one or two others.. (all this sounded like a good idea to me at the time ) I know I sound real stupid to you guys, but I used to be able to create unattended installs using RyanVM, NLite, and BTS..

This makes the system wait until the command file is done before executing the next thing. When I tried to put a reference to my own .cmd file in winnt.sif [GUIRunOnce], it was real ugly (v5.051 - option "G"). My cmd file seemed to run over something else that was executing. I always use "start /wait"...

Confusion reigns... I really have a need to create a new M2 CD tonight. The last time I tried it (v5.051), it did not create a [GUIRunOnce] section in winnt.sif, even though I selected "G" at the last.... I'm not even sure if the newest version creates a [GUIRunOnce] in winnt.sif anymore. The thing is, I have my own cmd file which I need to run just before the cleanup, and I used to be able to accomplish this by adding a couple of lines to that section in winnt.sif. So. If I want to create a new CD tonight, and (1) run a cmd file (installs some apps silently) just before cleanup, and (2) add a line to clean up my application installers directory (in $OEM$\$1\install): How do I now do this?? I think (Step by Step) - this is what I used to do - haven't been truly successful for several versions now: 1. Start with clean XP (SP2) image 2. RyanVM it 3. NLite it 4. Bashrat it: (can someone fill in the sub steps here, including manual changes both for fixing bugs and my cmd file and special cleanup?) I've looked at Bash's instructions, tried the latest, and have been unsuccesful (Is it because I tried to add my lines into a [GUIRunOnce] in winnt.sif - the same lines I've used OK before ?) Thanks Rob

Sorry, Bash... It's just that the last time (last night) I ran using M2, there was no [guirunonce] section in the resulting winnt.sif. I downloaded the latest of everything just before I ran this...

I can't keep up with these changes. Not only are the driverpacks themselves in a constant state of change, but now the methods of running the cmd files also... I used to add a couple of lines in winnt.sif to run a command file of my own. How do I do this now?

I plead gross ignorance.... Which "Rem bus extenders" line in what file? I looked in "Slipstream_DPM.cmd" and there is more than one line which begins with this string and references aliide in some way....

OK I'm REALLY confused. There hasn't been a new release (after v5049), but myself and others were getting the "aliide error" with this version when it first came out (I was using method 2, no WLAN drivers this time, so no long pathname prob). This is the first time I've ever had this problem; it is a problem which would occur with VMWare or VirtualPC. There was even a "fix" a few pages back which had you manually edit txtsetup.sif. When I was editing the file I "discovered" some blank [sourcedisksfiles] sections, you may remember. So now people are reporting success stories.... Bashrat, did you fix this problem without generating a new rev? In general, Whazzup? Where does this project stand, errors-wise? Whatever the case, Bashrat, thanks for the massive effort, anyway....

Bashrat: I compared several versions of Txtsetup.sif. Original/Vanilla versions have several [sourcedisksfiles] sections. In nLited versions, a couple of these sections are empty.... Sorry for the confusion, I've had successful results a few BTS revs back with these nlited images, so I guess this is a false alarm...

Found an extra [sourcedisksfiles] section in txtsetup.sif with nothing in it (v5049)... ...... wmerrenu.dll =1,,,,,,,2,0,0 eplrcz00.dll = 1,,,,,,,,3,3 [SourceDisksFiles] [Strings] MyPicturesScreenSaver = "My Pictures Screen Saver.scr" ViewChannelsSCF = "View Channels.scf" ....... Edit: This is one of several. There are 4 [sourcedisksfiles] sections in txtsetup.sif, and 2 are empty....

Bashrat: v5047 During Setup: Windows can't find WatchDriverSigningPolicy.exe Windows can't find setdevicepath.exe... .exe files are in ...\OEM\bin in BTS_DriverPacks_Base_V5047\UWXPCD_ROOT\M2\OEM\bin .exe files are missing from ...\OEM\bin in image after RUN_ME.cmd is executed... Method 2 Same nlited XPCD image as I used with v5045. This is new problem since then.... Edit (trying to reduce clutter): I "solved" this problem by manually copying the missing files to the image dir (see above). Then the install went through without stopping. However, I have reason to believe this is not all that is wrong... The nVidia control panel did not install (did with v5045). I don't think the chipset drivers installed... FYI Bashrat (This is from Everest): Driver Description NVIDIA GeForce3 Ti 200 Hardware ID PCI\VEN_10DE&DEV_0201&SUBSYS_88501462&REV_A3 VIA VT8377 Apollo KT600 Chipset Driver Description VIA Bus Master IDE Controller Hardware ID PCI\VEN_1106&DEV_0571&SUBSYS_50021458&REV_06 Driver Description VIA CPU to AGP2.0/AGP3.0 Controller Hardware ID PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00 Driver Description VIA Standard Host Bridge Hardware ID PCI\VEN_1106&DEV_3189&SUBSYS_00000000&REV_80 Driver Description VIA Standard PCI to ISA Bridge Hardware ID PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00 Driver Description VIA Rev 5 or later USB Universal Host Controller Hardware ID PCI\VEN_1106&DEV_3038&SUBSYS_50041458&REV_81 Driver Description VIA USB Enhanced Host Controller Hardware ID PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86 Driver Description USB Root Hub Hardware ID USB\ROOT_HUB&VID1106&PID3038&REV0081 Driver Description Realtek RTL8139/810x Family Fast Ethernet NIC Hardware ID PCI\VEN_10EC&DEV_8139&SUBSYS_E0001458&REV_10 Driver Description Silicon Image SiI 3112 SATARaid Controller Hardware ID PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_01 Driver Description Realtek AC'97 Audio for VIA (R) Audio Controller Hardware ID PCI\VEN_1106&DEV_3059&SUBSYS_A0021458&REV_60 Positives - Sata driver installed OK - "No Floppy install" works Audio driver control panel OK

I can no longer get the slipstream to work with method 2 using 5.045. There is a very confusing thread which seems to say that someone has fixed this, but does not say exactly how... Bashrat, could you release a REAL fix for this??? Rob

Bashrat: I checked, there is no $OEM$\$$\inf folder, even in the "successful trial" version (see my first post in this topic). I am using VIA KT600 chipset, so this is probably why it didn't bite me on the trial. I don't know what produces the inf folder, but it must not be nLite.... Should there be .inf files in there for other drivers than Intel chipset? (oops! Editing because I thought of something else) Besides, why would it ever want anything from "C:\DOCUME~1\Robert\LOCALS~1\Temp\..." ? Rob

Bashrat: I've had a successful install using V5044 (Look here), so I decided to slipstream 3 other versions that I am making UI's for. All three did this: Bashrat the Sneaky's DriverPacks Slipstreamer - STEP 3 BTS DriverPacks will be slipstreamed into your UWXPCD, using method 2. _ back-up of winnt.sif made... _ original SETUP.EX_ recovered... _ presetup.cmd deleted... _ back-up of txtsetup.sif made... _ back-up of dosnet.inf made... _ back-up of drvindex.inf made... _ DriverPacks slipstreamed... [method 2] _ replaced real setup by a fake one, copied presetup.cmd... _ txtsetup.sif file updated... _ DriverPack MassStorage slipstreamed... 2005/04/04 18:18:53 ERROR 3 (0x00000003) Accessing Source Directory C:\DOCUME~1\ Robert\LOCALS~1\Temp\DriverPack_Chipset_TMP\DP\C\I\ The system cannot find the path specified. The system cannot find the file specified. _ Intel Chipset .inf files copied to $OEM$\$$\INF... _ commands added to winnt.sif to install DriverPack Graphics A control panels... _ commands added to winnt.sif to install DriverPack Graphics B control panels... _ commands added to winnt.sif to install DriverPack Sound A control panels... _ commands added to winnt.sif to install DriverPack Sound B control panels... ################################################################################ Press any key to continue . . . Whazzup with the "Error 3?". I wasn't watching when my "successful" trial slipstreamed, so I don't know if this happened.... I'm not sure this problem would even affect the particular Mobo/component setup I am using, but it would surely bite someone, sometime... just FYI, Rob

Oops! What happens if you Google "I/OFlex PSA 150"? (My bad). Look at Koutech. Here's more info (from M$ System Info): Name Silicon Image SiI 3112 SATARaid Controller Manufacturer Silicon Image Status OK PNP Device ID PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_01\3&13C0B0C5&0&60 I/O Port 0x0000C000-0x0000C007 I/O Port 0x0000C400-0x0000C403 I/O Port 0x0000C800-0x0000C807 I/O Port 0x0000CC00-0x0000CC03 I/O Port 0x0000D000-0x0000D00F Memory Address 0xE3005000-0xE30051FF IRQ Channel IRQ 11 The sound is an on-board RealTek. Again, from System Info: Name Realtek AC'97 Audio for VIA (R) Audio Controller Manufacturer Realtek Status OK PNP Device ID PCI\VEN_1106&DEV_3059&SUBSYS_A0021458&REV_60\3&13C0B0C5&0&8D I/O Port 0x0000E400-0x0000E4FF IRQ Channel IRQ 11 I installed the test using a spare SATA drive in my workstation. I'll have to hook it back up to see about the yellow exclamation marks, but I seriously doubt there are any. My GEForce3 ti200 came up with the nVidia control panel as well Thanks Again! Rob

Very Cool Bashrat!! Using V5044, I just made a successful install using an iFlex PSA150 SATA (PCI) controller card (si3112). My system board is a Gigabyte GA7-VT600 (VIA KT600 chipset). The sound control panel came up, as well. The "AVRack" application for the sound was not installed - I am not sure if your intention was to include this... What this means for anyone is that you can "soup up" any computer (down to PIII) with a SATA drive (BIG improvement!!) using a controller board which cost me ~$17 US (NewEgg) and an 80 GB drive (~$60, same source)... Thanks Again Bashrat!! Rob

I've got a blue screen using BTS 5.032/ MassStorage 503.7.... This is a VIA Sata (not RAID). Here's the txtsetup.oem from a floppy that works: # # format for txtsetup.oem. # # General format: # # [section] # key = value1,value2,... # # # The hash ('#') introduces a comment. # Strings with embedded spaces, commas, or hashes should be double-quoted # # This section lists all disks in the disk set. # # <description> is a descriptive name for a disk, used when # prompting for the disk # <tagfile> is a file whose presence allows setup to recognize # that the disk is inserted. # <directory> is where the files are located on the disk. # [Disks] d1 = "VIA ATA/ATAPI Host Controller Driver", \VT6420, \PIDE\winxp d2 = "VIA ATA/ATAPI Host Controller Driver", \VT6420, \PIDE\win2000 d3 = "VIA ATA/ATAPI Host Controller Driver", \VT6420, \PIDE\winnt40 d4 = "VIA Serial ATA RAID Controller Driver ", \VT6420, \SATA\winxp d5 = "VIA Serial ATA RAID Controller Driver ", \VT6420, \SATA\win2000 d6 = "VIA Serial ATA RAID Controller Driver ", \VT6420, \SATA\winnt40 # This section lists the default selection for each 'required' # hardware component. If a line is not present for a component, # the default defaults to the first item in the [<component_name>] # section (see below). # # <component_name> is one of computer, display, keyboard, mouse, scsi # <id> is a unique <within the component> string to be associated # with an option. [Defaults] scsi = VIARAID_VT3149_XP # This section lists the options available for a particular component. # # <id> is the unique string for the option # <description> is a text string, presented to the user in a menu # <key_name> gives the name of the key to be created for the component in # HKEY_LOCAL_MACHINE\ControlSet001\Services [scsi] VIARAID_VT3149_XP = "VIA Serial ATA RAID Controller(Windows XP)",VT6420 VIARAID_VT3149_2K = "VIA Serial ATA RAID Controller(Windows 2000)",VT6420 VIARAID_VT3149_NT = "VIA Serial ATA RAID Controller(Windows NT4)",VT6420 VIAPDSK_VT4149_XP = "VIA ATA/ATAPI Host Controller(Windows XP)",VT6420 VIAPDSK_VT4149_2K = "VIA ATA/ATAPI Host Controller(Windows 2000)",VT6420 VIAPDSK_VT4149_NT = "VIA ATA/ATAPI Host Controller(Windows NT4)",VT6420 # This section lists the files that should be copied if the user # selects a particular component option. # # <file_type> is one of driver, port, class, dll, hal, inf, or detect. # See below. # <source_disk> identifies where the file is to be copied from, and must # match en entry in the [Disks] section. # <filename> is the name of the file. This will be appended to the # directory specified for the disk in the [Disks] section to form the # full path of the file on the disk. #=======================================# [Files.scsi.VIAPDSK_VT4149_XP] driver = d1, viapdsk.sys, viapdsk #dll = d1, setupvia.dll inf = d1, viapide.inf [Files.scsi.VIAPDSK_VT4149_2K] driver = d2, viapdsk.sys, viapdsk #dll = d2, setupvia.dll inf = d2, viapide.inf [Files.scsi.VIAPDSK_VT4149_NT] driver = d3, viapdsk.sys, viapdsk inf = d3, viapide.inf [HardwareIds.scsi.VIAPDSK_VT4149_XP] id = "PCI\VEN_1106&DEV_4149","viapdsk" [HardwareIds.scsi.VIAPDSK_VT4149_2K] id = "PCI\VEN_1106&DEV_4149","viapdsk" #=======================================# [Files.scsi.VIARAID_VT3149_XP] driver = d4, viasraid.sys, viasraid #dll = d4, setupvia.dll inf = d4, viasraid.inf [Files.scsi.VIARAID_VT3149_2K] driver = d5, viasraid.sys, viasraid #dll = d5, setupvia.dll inf = d5, viasraid.inf [Files.scsi.VIARAID_VT3149_NT] driver = d6, viasraid.sys, viasraid inf = d6, viasraid.inf [HardwareIds.scsi.VIARAID_VT3149_XP] id = "PCI\VEN_1106&DEV_3149","viasraid" [HardwareIds.scsi.VIARAID_VT3149_2K] id = "PCI\VEN_1106&DEV_3149","viasraid" # This section specifies values to be set in the registry for # particular component options. Required values in the services\xxx # key are created automatically -- use this section to specify additional # keys to be created in services\xxx and values in services\xxx and # services\xxx\yyy. # # <key_name> is relative to the services node for this device. # If it is empty, then it refers to the services node. # If specified, the key is created first. # <value_name> specifies the value to be set within the key # <value_type> is a string like REG_DWORD. See below. # <value> specifies the actual value; its format depends on <value_type> [Config.VT6420] value = "", Tag, REG_DWORD, 1 #HP-Delete following line #value = "Parameters\PnpInterface", 5, REG_DWORD, 1 With my newly minted Unattended CD, setup finds my viaraid, formats, loads drivers,etc. and I get a BSOD (7B) at first reboot immediately after the Windows XP screen with the blue dots.... You seem to have support this device, but I don't know how to find out what is wrong. I'm loading the OS the old fashioned way (Press F6 w/ Floppy in drive), and it is working fine.... The file date on the driver file visraid.sys is 6/12/2003.

Thanks! Your driverpacks already include the sound and IDE/Raid drivers for NForce and VIA (I used the "Manual Fix 2" you made). So, exactly what drivers for NForce would I need? For Nforce, I used to have drivers in the following directories: 000_NFIDE 01/13/2004 11:36 AM 5 disk1 01/13/2004 11:36 AM 291,328 idecoi.dll 03/23/2004 09:12 AM 9,655 nvata.cat 03/10/2004 11:42 AM 3,552 nvatabus.inf 01/13/2004 11:36 AM 63,744 NvAtaBus.sys 01/13/2004 11:36 AM 31,232 nvcoi.dll 02/25/2004 09:52 AM 464 nvide.nvu 03/23/2004 09:12 AM 9,651 nvraid.cat 01/13/2004 11:36 AM 2,080 nvraid.inf 01/13/2004 11:36 AM 57,472 nvraid.sys 01/13/2004 11:36 AM 18,432 nvraidco.dll 01/13/2004 11:36 AM 7,168 NvRaidEnu.dll 01/13/2004 11:36 AM 239,104 NvRaidMan.exe 01/13/2004 11:36 AM 83,456 nvraidservice.exe 01/13/2004 11:36 AM 6,144 NvRaidSvEnu.dll 01/13/2004 11:36 AM 302,080 NvRaidWizard.dll 01/13/2004 11:36 AM 37,888 NvRaidWizardEnu.dll 02/25/2004 09:52 AM 159,744 nvuide.exe 01/13/2004 11:36 AM 25 RegRaid.bat 04/02/2004 02:40 PM 4,360 txtsetup.oem **** I don't think I will need the above ************ 000_NFMEM 03/21/2004 01:30 AM 1,217 nvmctl.nvu 04/18/2003 09:40 AM 8,149 nvmemctl.cat 04/09/2003 05:39 PM 2,562 nvmemctl.inf 04/12/2004 09:26 AM 172,032 nvumctl.exe 000_NFSMBUS 11/26/2003 02:54 PM 7,573 nvsmb.cat 04/12/2004 08:06 AM 789 nvsmb.nvu 11/20/2003 04:46 PM 1,223 nvsmbus.inf 04/12/2004 08:06 AM 172,032 nvusmb.exe What VIA drivers would I use? I used to use: 000_VIA 07/30/2003 12:45 AM 8,850 viaagp1.cat 07/02/2003 04:42 AM 4,187 VIAAGP1.INF 07/02/2003 04:42 AM 27,904 VIAAGP1.SYS 08/03/2001 05:16 PM 32,768 VIAIDE2K.DLL* 10/18/2001 12:00 PM 1,573 VIAIDEXP.INF* 10/18/2001 12:00 PM 6,144 VIAIDEXP.SYS* 07/01/2003 11:55 PM 12,219 viamach.cat 06/13/2003 03:03 PM 9,964 VIAMACH.INF 11/07/2001 09:05 AM 7,161 VIAMINI.CAT * I'm guessing I'll need to remove the above - is this correct? Also, where do I start in the process after I 7zip the drivers? Do I have to start from scratch? Thanks again Rob

Question for Bashrat: I'm using the driverpacks and NLite for the first time. Previously, I had an Unattended install for XP SP2 with RyanVM's update 1.02 in it. Also, I had nVidia NForce drivers (Chipset, sound, disk) and VIA drivers (chipset, sound, disk) via the "OemPnPDriversPath" in winnt.sif. I notice this Bahsrat/nLite version doesn't seem to use this. What is the easiest way to include the chipset drivers for NForce and VIA in this image? Thanks Rob

Thanks. I did the same exact thing for the XP Home OEM that I did for Pro Corporate and Pro OEM. I edited the txtsetup.sif. I even checked to make sure the edits were on exactly the same line (right after [Files]) in the DOSNET.INF file and in the same area in txtsetup.sif... I did read this entire thread, and I wonder if some of these other Framedyn complainers aren't revealing that they are using XP Home. BTW, I had whined about Taskkill earlier. It turns out I had added it to my earlier Home install. Dump it into i386, and another txtsetup.sif edit... Are there issues when you slipstream SP2 into a previously (SP1) slipstreamed image? I've read there aren't, but I've also seen hints ther might be...

At the risk of p***ing somebody else off, here goes: I've maintained 3 versions of WinXP (SP1) Unattended installs for several months: (1) XP Pro Corporate, (2) XP Pro OEM, and (3) XP Home OEM. I recently decided to get with the program and make installs for XP SP2, especially now that there are "pre SP3 Hotfixes" . I decided to use RyanVM's excellent SP2 Update Pack. So I did. Everything works OK for Pro Corp and Pro OEM. However, XP Home OEM gives me the dreaded "Framedyne.dll" and "srclient.dll" errors. One thing that is different about the Home ver. is that I started with a SP1 OEM CD (then slipstreamed SP2 on it, no errors). Is there some feature which is missing in the Home ver, that is needed for one of the elements of RyanVM's update pack? BTW, no, I did not use nLite..... Framedyn.dll. Slowly he turned, step by step.... But 2 out of 3 ain't bad, is it??

I've maintained 3 versions of WinXP (SP1) Unattended installs for several months: (1) XP Pro Corporate, (2) XP Pro OEM, and (3) XP Home OEM. I recently decided to get with the program and make installs for XP SP2, especially now that there are "pre SP3 Hotfixes" . I decided to use RyanVM's excellent SP2 Update Pack. So I did. Everything works OK for Pro Corp and Pro OEM. However, XP Home OEM gives me the dreaded "Framedyne.dll" and "srclient.dll" errors. Also, "taskkill.exe", which I use to kill AdAware SE personal, doesn't work for this version only. One thing that is different about the Home ver. is that I started with a SP1 OEM CD (then slipstreamed SP2 on it, no errors). Is there some feature which is missing in the Home ver, that is needed for one of the elements of RyanVM's update pack?

(I accidently posted this in the XP forum, I think it really belongs here) How about these: Q824151 (11th October 2004) Vulnerability in WebDAV XML Message Handler Could Lead to a Denial of Service Download - 942KB Q841553 (12th October 2004) Vulnerability in NetDDE Could Allow Remote Code Execution Download - 706KB Q840987 (12th October 2004) REPLACES: Q811493 and Q824141 Security Update for Microsoft Windows Download - 5902KB Q873376 (12th October 2004) REPLACES: Q329048 Vulnerability in Compressed (zipped) Folders Could Allow Remote Code Execution Download - 475KB Q841356 (12th October 2004) REPLACES: Q821557 and Q839645 Vulnerability in Windows Shell Could Allow Remote Code Execution Download - 4280KB Q834707 (12th October 2004) Cumulative Security Update for Internet Explorer Download the Update for IE6 SP1 - 3126KB Q873377 (14th October 2004) REPLACES: Q832894 Update Rollup for Internet Explorer SP1 Download the Update Rollup for IE6 SP1 - 3136KB Q824151 and Q841553 are listed as "Important" security issues on M$ website. The rest are "Crititcal". I suppose Q834707 replaces the current CSU for IE6 (download is for IE6 SP1). I'm getting a little confused about all the hotfixes, so could someone help with this? I've done a little of the grunt work (posting these in the format used by Aaron)

How about these: Q824151 (11th October 2004) Vulnerability in WebDAV XML Message Handler Could Lead to a Denial of Service Download - 942KB Q841553 (12th October 2004) Vulnerability in NetDDE Could Allow Remote Code Execution Download - 706KB Q840987 (12th October 2004) Security Update for Microsoft Windows Download - 5902KB Q873376 (12th October 2004) Vulnerability in Compressed (zipped) Folders Could Allow Remote Code Execution Download - 475KB Q841356 (12th October 2004) Vulnerability in Windows Shell Could Allow Remote Code Execution Download - 4280KB Q834707 (12th October 2004) Cumulative Security Update for Internet Explorer Download the Update for IE6 SP1 - 3126KB Q824151 and Q841553 are listed as "Important" security issues on M$ website. The rest are "Crititcal". I suppose Q834707 replaces the current CSU for IE6 (download is for IE6 SP1). I'm getting a little confused about all the hotfixes, so could someone help with this? I've done a little of the grunt work (posting these in the format used by Aaron)