IcemanND

I hate saying this, search, search , search.... http://www.google.com/custom?hl=en&cli...fix&spell=1 And Please turn off the CAPS.

Patience Express, got give us a chance to wake up and get to the forums. does the registry file work locally on w2k machines?

only thing I have installed is 7-zip, and I had reregistered the zipfldr.dll when I was trying to get something to work the last time.

That's the only thing I have done since I did it was reboot.

ok now this is weird. It worked great for me when I posted it, tested it multiple times on two different machines. Now I can't get it to work.

don't add the extension: C:\copy foo.zip\*.* myfoo should be C:\copy foo\*.* myfoo

I'm assuming you are not booted into safe mode in which the installer service does not run by default. In which case, try running Dial-a-fix and have it repair the windows installer.

will it boot to safe mode? Do you have the option from the boot menu to disable to reboot on error? That way you can see the BSOD error message.

[GUIDE] Creating WIM images of Windows XP for system deployment using, Downloadable tutorial http://www.msfn.org/board/index.php?showto...st&p=674778 Doesn't deal with WDS though, that will be another guide I will post later, have to get a system I can use for test WDS on first. All my test systems are currently dedicated to another project.

it depends upon the application I have found some that do not like to install via network, even though they will try. If you are using CMD scripts to run the installer you need to add a setlocal statement to enable extensions so that UNC paths are accepted. You may also find that some installers do not like UNC paths contained in switches.

That was "USUALLY" not always, there sometimes even the windows filters get corrupted. Export the key first before you modify it if you so desire. Changing this key will not prevent windows from booting, and the reason I had you rename the value name is so you could just change it back if it didn't fix it. If I had a dollar for every time I did this and fix a code 10 or code 39 error I'd be vacationing in a much cooler location right now.

85°F/ 52%RH, Sunny, will hit the mid 90's today and maybe a random cloud. TOOOOO HOT.

why not just deny all permissions to the registry value so that it can't be changed?

http://www.performance-pcs.com/catalog/ind...oducts_id=21193 Google: ULT40011 you might turn up someone in your area. I personally used the do it yourself method on an old Dell Gxa a number of years ago and ran it like that for almost 2 years without a problem. Nothing like running a PII 300 with 4 cd/dvd, a zip, and 8 hard drives attached. Made for a mess of cables coming out of the back.

open regedit go to HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318} Rename UpperFilters to oldUpperFilters Rename LowerFilters to oldLowerFilters Remove the CD's from the device manager and then search for new hardware and let them be readded. See if they work, if the do on of the filters installed is missing or corrupted. Usually one for your cd burning software.

That's about 8 lines of code in vbscript or auto it. What registry key?

I've found with the IBM/Lenovo's when you capture a disk image of the machine you have to use the /IB (image Boot) switch in order for the image to deploy back to the system and have the recovery partition work.

I bet that "certain video card" is an Intel? If that is the case this http://support.microsoft.com/kb/910678 may help, unfortunately you have to call to get the hotfix, or find it somewhere else online. Or maybe this one: http://support.microsoft.com/kb/883667

That would be Page 6 step 6, the second xcopy command copies imagex to the mounted image, then you have to commit the changes when you unmount it (step 10).

That will make it easier, 2000 will recognize the NT install and configure dual boot correctly, nt4 will not recognize 2k so you would have to repair the boot loader.

Here's the command file I use to make a dual boot PE 2.0 and Xp system with 2 different partitions. Remove the third section if you don't need legacy (xp or older) booting. bcdedit -createstore c:\boot\bcd bcdedit -store c:\boot\bcd -create {bootmgr} /d "Boot Manager" bcdedit -store c:\boot\bcd -set {bootmgr} device boot for /f "tokens=3" %%a in ('bcdedit -store c:\boot\bcd -create /d "Windows PE" -application osloader') do set guid=%%a bcdedit -store c:\boot\bcd -set %guid% osdevice partition=c: bcdedit -store c:\boot\bcd -set %guid% device partition=c: bcdedit -store c:\boot\bcd -set %guid% path \windows\system32\boot\winload.exe bcdedit -store c:\boot\bcd -set %guid% systemroot \windows bcdedit -store c:\boot\bcd -set %guid% winpe yes bcdedit -store c:\boot\bcd -set %guid% detecthal yes bcdedit -store c:\boot\bcd -displayorder %guid% -addlast bcdedit -store c:\boot\bcd -create {legacy} /d "Windows XP" bcdedit -store c:\boot\bcd -set {legacy} device boot bcdedit -store c:\boot\bcd -set {legacy} path \ntldr bcdedit -store c:\boot\bcd -displayorder {legacy} –addlast bcdedit -store c:\boot\bcd -default {legacy} bcdedit -store c:\boot\bcd -timeout 5 bootsect /nt52 all

if you use vmware you can add a floppy to the VM and have it create a image to use for the floppy instead of a physical drive. Not sure about virtual pc, never tried it with that.

http://www.csharp-station.com/ has some good tutorials.

setup a vm with a floppy in it, extract the floppy image to the virtual floppy drive, then copy them out of the vm to your windows installation. Or install a virtual floppy drive and do the same thing without the VM. Then integrate them into your installation cd.

Welcome to MSFN. As Stoic stated please don't double post. Duplicate Deleted.