cfeedback

You will need to get into the BIOS in order to disable the onboard video. If you're not able to do this you might be SOL.

Didn't ever come across this problem. Most of the time it would give an error in the dos based setup if anything was wrong. When you say it "finishes setup without fault" you mean the windows portion of the setup? You could post the relevant portions of your .sif files for someone to look over...also are you doing other unattended stuf - registry edits, other apps, etc? You might try starting from scratch, get a working ISO with the RAID drivers first, then build on it from there.

nvraid.sys = 1,,,,,,4_,4,1,,,1,4 - compressed nvraid.sys = 1,,,,,,_x,4,1,,,1,4 - uncompressed I might not have been clear on that in my initial post. In theory it should work either way in practice I've only tried compressed so YMMV. Haven't spent much time on this site lately as my slipstream DVD is a thing of beauty that almost brings a tear to my eyes. I spend my time now making them for friends' PCs, or at least trying to convince them that they need it. (Friend: Why would I want to reinstall Windows again?) Glad this thread has helped a number of people!

I would have to agree that you should give Bashrat's pack a try as it looks like it's working fairly well now and he's done the hard work for you. I posted this because at the time there were still a few issues with it and NVRAID and I needed something to work RIGHT away. Plus, I just needed to go over the process I went through after a grueling two days of frustration and countless windows installs (thank god for dvd-rw's). Might I also suggest you ignore anything and everything MSI gives you driver/application wise (well..excluding your BIOS updates of course) and get the RAID drivers from the nvidia package: http://www.nvidia.com/object/nforce_udp_winxp_5.10

Well, I'm never one to leave well enough alone and something I've done from my last good build (ya, I should test each change once at a time I guess) is causing this error when my start.cmd runs. Anyone have a clue as to the most likely cause of this? Various info... [COMMANDS] "REGEDIT /S regtweaks.reg" "useraccounts.cmd" useraccounts.cmd is setup identical to what's in the guide... Windows Registry Editor Version 5.00 ;Disable Automatic Restart in the event of a BSOD [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl] "AutoReboot"=dword:00000000 ;Speed up shutdown [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control] "WaitToKillServiceTimeout"="3000" ;Disable the Desktop Cleanup Wizard [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\CleanupWiz] "NoRun"=dword:00000001 ;Disables Windows Tour bubble popup [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Applets\Tour] "RunCount"=dword:00000000 ;Disable Remote Registry Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteRegistry] "Start"=dword:00000004 ;Disable Anti-virus Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "AntiVirusDisableNotify"=dword:00000001 ;Disable Firewall Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "FirewallDisableNotify"=dword:00000001 ;Disable Automatic Updates Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "UpdatesDisableNotify"=dword:00000001 ;Disable Indexing Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cisvc] "Start"=dword:00000004 ;Disable Update Device Driver Wizard [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoDevMgrUpdate"=dword:00000001 I won't list my start.cmd (set to run from GUIRunOnce) unless someone thinks it's necessary...I can click continue through the errors and it fails on every installer, all of which work in a previous build. I appreciate anyone who can save me a lot of time/effort on troubleshooting this!

[Version] Signature=$CHICAGO$ [DefaultInstall] AddReg = CDImage AddReg = Mount DelReg = Daemon [CDImage] HKCR,"Folder\shell\MakeBootISO\command",,,"CDIMAGE.EXE -LWINDOWS -YD -N -H -X -B%11%\xpBoot.img -OCI -M -D %here% %24%\BootImage.iso" HKCR,"Folder\shell\MakeDataISO\command",,,"CDIMAGE.EXE -LDATA -YD -N -H -X -O -M -D %here% %24%\DataImage.iso" [Mount] HKCR,".ISO",,,"ISO_Image" HKCR,".CUE",,,"ISO_Image" HKCR,".CCD",,,"ISO_Image" HKCR,".BIN",,,"ISO_Image" HKCR,"ISO_Image\Shell\Mount\Command",,,%16422%\D-Tools\"daemon.exe -mount 0,%1 [Daemon] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","DAEMON Tools-1033" [Strings] here = """%1""" I thought it was the same as what you listed, but I could've made a mistake...thanks for the help! BTW I didn't mention it, but it DOES end up working - I can right click to mount an image. I just don't know why it launches another installer!

I don't have any firm reason why, but I'd prefer not to use nLite. I believe I can remove the bluetooth support from XP manually by removing these files, but the problem is during the DOS based setup I have to tell it to skip these files it can't find. Can someone tell me exactly what file I need to edit? txtsetup or something I'm guessing? files removed from I386: bthusb.sy_ bthprint.sy_ bthport.sy_ bthpan.sy_ bthmodem.sy_ bthenum.sy_ bthspp.in_ bthprint.in_ bthpan.in_ bth.in_ bthserv.dl_ bthci.dl_ bthprops.cp_

Has anything changed on this method (which I love btw, thanks!) with 3.47? I have 2 issues: first, when I run Daemonscript.msi with either the /qb or /qn switch fromt start.cmd it installs into C:, yet when I run it manually it installs into \Program Files\ as it should. Second, my rundll32 line does all sorts of crazy stuff so I must be doing something wrong. It will usually load another installer than already ran from the start.cmd, such as my ATI Remote Wonder or Logitech Setpoint software. Thanks for any help! ECHO. ECHO Installing DaemonTools v3.47 ECHO Please wait... start /wait %systemdrive%\Install\DaemonTools\DaemonTools.msi /qn REBOOT="ReallySuppress" start /wait %systemdrive%\Install\DaemonTools\Daemonscript.msi /qb start /wait %systemdrive%\Install\DaemonTools\DaemonDriveInstall.DaemonScript rundll32 setupapi,InstallHinfSection DefaultInstall 128 %systemdrive%\Install\DaemonTools\DaemonTools.inf

doesn't that defeat the purpose of an unattended installation? also, without the SP2 bluetooth support I'm guessing my mouse/keyboard won't work until the Widcomm stack is installed, which will basically be a pain in the butt as I'll have to connect a regular ps/2 set. Don't tell me that's the most elegant solution possible...there's too many smart people that read these forums! On the nLite method I tried before, when I got the graphical windows installer services.exe could not find MSVCP60.dll. I'll have to try it without asking nLite to integrate the widcomm crap automatically next...

Sorry I thought that was clear...in any case, I'm using the main ATI setup.exe that you get when you extract this package: http://www2.ati.com/drivers/wxp-w2k-ccc-8-...25a-017633c.exe

What are the chances of my being able to integrate this into my XP install? Having all sorts of problems getting it to play nice with SP2. My logitech bluetooth mouse/keyboard combo works with the SP2 drivers but I lose out on some of the features. Oh, and for some reason the SetPoint drivers won't install unattended unless the widcomm stack is installed first. I can install the stack after windows is up and running but it doesn't recognize the bluetooth USB hub like it did before. The method I'm trying now is to use nLite to remove the XP Bluetooth drivers, then I picked it to add the widcomm INF file. I'll be amazed if it works the first time. Other ideas I had were to include the widcomm files in either I386\$OEM$\... or in the regular $OEM$\$\Driver\ directory. I'm not sure they'll install without the setup.exe there's like 74 files with the installer. Also, if I wanted to remove the Bluetooth support from my XPCD manually, any idea which files they are? I know about the bth.inf (bth.in_) file - would removing that be enough? Thanks for any ideas!

Ok first I'm installing this from the start.cmd in [GuiRunOnce]. It's the full package. YMMV if your setup isn't the same...I'm really no expert. Run the base setup.exe (the one after you've extracted everything from the ATI download) with the -R switch. The setup.iss it generates looked like this for me: [InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{43801800-CFEE-11D2-A41B-006097B55AD3}-DlgOrder] Dlg0={43801800-CFEE-11D2-A41B-006097B55AD3}-SdWelcome-0 Count=3 Dlg1={43801800-CFEE-11D2-A41B-006097B55AD3}-SdLicense-0 Dlg2={43801800-CFEE-11D2-A41B-006097B55AD3}-SdOptionsButtons-0 [{43801800-CFEE-11D2-A41B-006097B55AD3}-SdWelcome-0] Result=1 [{43801800-CFEE-11D2-A41B-006097B55AD3}-SdLicense-0] Result=1 [{43801800-CFEE-11D2-A41B-006097B55AD3}-SdOptionsButtons-0] Result=101 You need to add BootOption=0 on the last line. I also found that I needed to go into the \WDM\ directory, run setup.exe -R again, and put its setup.iss there. The installers in \CPanel\ and \Driver\ already have them. This setup seems to work flawlessly for me. Run this first in your start.cmd file or second if you install .NET from the start.cmd as well.

I had the same problem at first, at least with it asking to restart. Didn't have a problem with it asking for the express install. In any case, I had to make one more setup.iss that one of the components was missing. In... \$1\Install\Catalyst\ I have a total of 4 setup.iss files...one in the main directory, and ones in CPanel, WDM, and Driver. While I don't know if they're all necessary, it works for me...make sure they all have the BootOption=0 line and if you're missing any of them you can create one by running that individual installer with the -R switch.

Yeah, the built-in firewall is actually decent now...I'll agree with that. He's not using ZA but rather Norton Internet Security. I'm more thinking along the lines of the extra/demo versions of programs a lot of CDs have on them. I can just forsee him installing some 2 year old version of a program and I was trying to minimize any future conflicts. On the topic of firewalls, I'd like to use the built-in one that his K8N Neo Platinum MB has but it's a bit buggy now - maybe in a future driver update it will be worthwhile. In any case, you bring up some valid points. I'll have to give it some thought. I was just trying to be cautious and keep him off the "bleeding edge" of technology.

Are you also one who doesn't buckle your seatbelt in your car because it takes too much time?I guess I should take time to explain myself better. This is a PC I built for my non-technical minded uncle. While I don't have the offending mpegport.sys, I don't think that's the only problem out there. On the AMD forums I've seen people report crashes from certain other programs - ZoneAlarm comes to mind. He's the kind of guy who'd buy a program and install everything on it even if it was a 2 year old version. It's far easier for me to disable it now and tell him 6 months from now to enable it, than to risk him doing something stupid that might cause a conflict. I can just hear the phone conversation in my mind..."safe mode? ok I hit the F key then 8?" and it would probably go downhill from there...