Netman66

If you can access your A: drive then throw in a floppy. Run this command to output a list of files to a text file on your floppy: (Make sure you're at the root of C:) dir *.jpg /s > a:\jpeg.txt Alter the command for each type of picture file you're looking for: dir *.tif /s > a:\tif.txt dir *.bmp /s > a:\bmp.txt etc, etc, etc

It sure does. Retail and OEM builds use different media. Neither Key works on the other builds. You wouldn't be able to build an image from your VLP media and use anything but a Volume Key on it. The way I see it, you'll need 3 images - one for each build type.

Try changing the password to "Default1" You may have a password policy affecting it somehow.

Have you tried enabling the Guest account on the print "server"?

For those of you interested in getting Aero Glass working on a mid-range laptop adapter, I've taken the time to document it. <http://msmvps.com/blogs/netman66/archive/2006/11/26/vista-ultimate-with-nvidia-go5200-there-is-hope.aspx> I hope this helps someone! Cheers, Paul

Find the services.msc in System32. Right click it and select Author. On the File menu select Options. You now have another tab called Console. Uncheck the box for "Do not save changes to this console". That should take care of things. NM I should also add that as long as that box is unchecked you will be prompted to save changes every time you exit the console. To avoid this, make you changes once and save them then reverse the procedure above and re-check that box.

These are fantastic! How about a Registry Search and Replace tool? This would be awesome. I've asked MS for 3 years to fix Regedit so you can Find and Replace and they won't entertain the idea. PowerQuest Partition Magic used to come with something similar so when you shrunk a partition to add another and move your data/programs you could change the drive letter in the Registry. Would that be hard to do?

I've looked through all the DLLs that Winlogon seems to refer to and cannot find the bitmaps I see on the CTRL+ALT+DEL screen. I even checked MSGINA and all the GINA dlls I could find. I'm using Reshacker to open them and check the bitmaps but none look remotely close. Any idea where in the Registry this is referred to?

I have Biologon3 installed and in use. It replaces the gina with it's own. Is XPize *smart* enough to leave it alone or will it replace it? If it replaces it, does it break Biologon? I haven't installed it yet since I want to get some answers about this first. Thanks. NM

Nevermind the request for 0.5.5 - you've posted it already, sorry. I have noticed one interesting thing which *may* prompt the Wizard to show up even if the drivers are located in the DevicePath path. In the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup ...there is a value: Installation Sources ...which seem to hold paths to the drivers that were installed last. If these values conflict, it may prompt the Wizard to appear. I wonder if capturing, deleting then repopulating that value might work??

I have no problem helping you out with this - I see it as very useful if it works the way it's supposed to. I will test this extensively on Tuesday when I'm back in front of the images I'm working on. I have 9 different machines at my bench (6 different desktops and 3 different laptops) so I should be able to stress test this to the max. Can you Upload 0.5.5 with all minor correction so I can use the latest cleaned build? Incidently, what is the maximum path length for this registry key? I think it's 4096 characters - can you confirm? Also, if you can write some logic into your code to display the length of the path (in the window) it will add to the registry it would be very helpful as a visual indicator of how close we are to the limit. Thanks, NM

I was also wondering about the Add New Hardware Wizard. I was under the impression that after the Registry was pointing to the correct location that the hardware should just install without asking for any manual input as long as all the correct drivers were there. Is this not the case? If that's how it works, then we need to figure out how to automate that as it defeats the purpose of unattended installation. So far so good though. It seems to be doing what it's supposed to other than the wizards.

Just tried it again on another machine and it works fine this time! I suspect when I downloaded and overwrote the old version it didn't do it correctly. Will let you know on Tuesday whether this clean download solves it. Thanks for all the assistance and fixes!

I'm now getting the script error again.

Well, that was a little different now. The script failed with the following error: Using the following INI: [iNFO] Start=Automatic Mode=Standard Drivers_drive=C Drivers_dir=\Asus Device_manager=On Method=RegistryDevicePath Logging_to_file=Yes Logging_option=Advanced Drivers_Packed=No Copy_drivers=No Copy_where= Delete_drivers=No Create_backup=No Leave_Registry_Entries=No Debug=Yes [Advanced] Registry_Path=END And here's the logfile: [23:58:06] - =================== Log Start: TEST [23:58:06] - Starting program on TEST. [23:58:06] - Detecting Windows version - Windows XP x32 [23:58:06] - Checking for drivers directory existance. [23:58:06] - Directory with drivers (C:\Asus) exist. [23:58:06] - Detecting number of devices in system. [23:58:06] - Found 137 devices of which 1 has problems. [23:58:06] - Automatic start used - GoGoGo.. [23:58:06] - Setting Driver signing to OFF. [23:58:06] - Setting path into registry using RegistryDevicePath method. [23:58:06] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: Volume in drive C has no label. [23:58:06] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: Volume Serial Number is 7C1C-7789 [23:58:06] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: [23:58:06] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: Directory of C:\Asus [23:58:06] - DEBUG in REGISTRYDEVICEPATH FUNCTION 1: Directory of C:\Asus I hope this means something to you!

It's English. We do have the MUI installed though. I really want this to work. We support too many different hardware platforms to have to manage images for. A single image is the goal and your utility would be perfect if we could get it working. Thanks for the effort and I hope we can put our fingers on the issue and solve it. NM

OK, here's what I've found. Running SetDevicePath.exe against my Drivers folder correctly populates the registry. If I run your utility now, it removes everything, but doesn't put any entries at all except the default entry. It appears the device path component of your utility doesn't want to work for me.

OK, I've got it to remove the existing default entry when Registry_Path=None and add the defualt back in when it set to BEGIN or END. So the issue isn't with the key. I dumped an unpacked driver into the root of my driver folder specified in the hardware INI (C:\A). The driver is relevant to the machine and one that is missing (the video) so it should pick it up, but it doesn't seem to want to add the path. Any ideas? Also just noticed that Advanced logging (in the new build) stopped logging removal events or the tool quit removing hardware!

OK, ran the new build with the attached INI and LOG file. Still no modification to the Registry. Permissions on this key indicate Admin has ZFull Control and the normal User has Modify. We're running this as Admin. The driver source was shortened down to see if it was a path length issue with no change. I'm quite sure this will all work if the registry key would get modified. Thanks in advance. [iNFO] Start=Automatic Mode=Standard Drivers_drive=C Drivers_dir=\A Device_manager=On Method=RegistryDevicePath Logging_to_file=Yes Logging_option=Advanced Drivers_Packed=No Copy_drivers=No Copy_where= Delete_drivers=No Create_backup=No Leave_Registry_Entries=No Debug=No [Advanced] Registry_Path=None [03:00:53] - =================== Log Start: TEST [03:00:53] - Starting program on TEST. [03:00:53] - Detecting Windows version - Windows XP x32 [03:00:53] - Checking for drivers directory existance. [03:00:53] - Directory with drivers (C:\A) exist. [03:00:53] - Detecting number of devices in system. [03:00:53] - Found 126 devices of which 5 have problems. [03:00:53] - Automatic start used - GoGoGo.. [03:00:53] - Setting Driver signing to OFF. [03:00:53] - Setting path into registry using RegistryDevicePath method. [03:00:53] - Drivers path was set successfully into registry. [03:00:53] - Removing unknown hardware from system. [03:00:54] - Unknown devices were removed successfully. [03:00:54] - Starting Device Manager. [03:00:54] - Forcing system to detect Plug & Play Devices. [03:00:54] - System is now detecting and installing drivers for your hardware. Wait!

I am also having the same issues as ty628659. The tool states that it's adding the Registry Paths and that they are successful, however the path in the registry is never changed. What key are you changing? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion :: DevicePath If so, there's no new entries.