dobbelina

I was wondering, is there an application switch list avaliable somewhere ? I was thinking basically a "runonce.cmd on steroids" kinda thingy. Where one doesn't have to browse thru several web pages to find them. Since i'm on dial-up (even though interesting) it's timeconsuming to have to search for each and every app switch in the forums. If there is such a list, and I missed it, i'm sorry for bringing it up. I'm not saying starting separate threads for each and every app is a bad idea, just it would be very convenient to have such a list. Preferrably on a forum page where replies aren't allowed. Such a list could be updated "on the fly" for new switches by a moderator or admin for example..

Vomad, go and have a look at "Sharks file repository", there's an SCSI Pass Through Direct driver, that makes it possible to install Alhohol 120% without reboot. Maybe it's something for you: http://sharksfiles.doitrightconsulting.net/

Just to add to the discussion. Acronis "Universal restore" can restore to any hardware. It obviously has all the "Hal's" as there's no limitation of restoring to ACPI/non-ACPI systems. Wtth other words, one image to all systems.... One thing that's a shame though is it's Only working when restoring TI images. If that app where standalone, i'd be a happy camper If you guys can do something like that, i'll take off my hat for you !

Ok, thanks for that info. And yes you are right, i've had a closer look at those inf files pointing to subfolders in UIU, It's only ATI Display Information file's that does that. Seems ATI packs their drivers that way. Thanks everyone for your awesome support

Ok, thanks for that clarification Regarding the UIU, i'm not sure wether they have edited the inf files or not. Almost all of their (i don't really mean theirs) drivers are put in the root folder at this location: C:\Windows\inf\UIU Then there are about 50 subfolders with only a few drivers in them each. The folders are named A0100,A0101 etc trickling down to B_25699. The reason I think they have edited the inf files is cause some of them, located in the root, points to some of these subfolders, ex: [sourceDisksNames.x86] 1 = %DiskId%,,,.\B_14575 [sourceDisksNames.ia64] 1 = %DiskID%,,,.\B_14575 PS. If I would to exceed the byte limit by doing some drastic "foldering", maybe regedit would let me know ? Thanks for answering

Hi again ! After downloading a few of the DP's i've noticed there's a whole lot of subfolders. My question is, how do I check accurately if i have exceeded the 4096 bytes limit in the device path ? The shortest path I can come up with is basically C:\D The reason i'm asking is, cause i'm scared i'll put to much data in there if I add the whole tjobang.... (perhaps also modem and monitor) I'm not restrained by a 700 mb limit as i'm using diskimages. I've noticed after examining the driver pack that came with the "Universal imaging utility" from binaryresearch.net, that they put almost all the drivers in the root folder. They only create subfolders for files with identical file names. I guess if one do like that, one can squeeze a whole lotta drivers into a very small path... But offcourse they'll be difficult to find. Not sure, but I think they edit the [sourceDisksNames] to point to folders of their choosing for the identical file names, perhaps you could elaborate on that since it doesn't really make sense to me.... So how can I check this path thing out "down to a T" ? Also, would renaming the inf files be good or bad ?

Ok, thanks for the feedback. That's great to know. Sometimes I fix computers for other people, and guess how often I get met with the comment: "were there supposed to be CD's coming with the computer ?" A great timesaver for me, no need to go on-line and loose time on driverguide.com PS. if anyone wonders, Acronis universal utility also scans the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion" path for those scsi drivers, so if you got it configured correctly with SetDevicePath.exe, it'll install them onto your diskimage.

Ok, I figured it out, it should not be: SetDevicePath.exe %SystemRoot%\D it should be: SetDevicePath.exe %SystemDrive%\D What about if I would just wanna keep the drivers (un-compressed) on a CD, and use that as a source when installing ? (Not for mass storage drivers offcourse) Is that possible ? I mean i've seen the %CDDRIVE% variable mentioned somewhere, or is this un-neccessary. If i pop the CD in, enter the device manager and right click those yellow question marks and tell it to "Look in the CD drive" is that enough ? I mean will it look thru all the sub-folders, or only the one i'm pointing to ?. I understand this will not be "plug and play", but rather a neat way to find a driver when it's needed.

I think the nicest tool to detect hardware info, is without question Everest from Lavalys.

Ok, thanks. Ehhh, what would I put into the setpaththingy if I put the "D" folder in the root ? Would this be correct: SetDevicePath.exe %SystemRoot%\D

Hi ! I've just d/l'ed Acronis latest product named "Universal restore". It's an awesome tool that let's you install diskimages to any hardware. It solves the "Hal and scsi" problem by loading these drivers into the system before the restored image boots onto the new hardware. Now, i was wondering, i would like to make an image with the driverpacks.net driverpacks, so that these drivers are avaliable as "plug and play". From reading some previous topics is this how i should go about doing this ?: 1. Download the driverpacks and copy them to a folder named "D" inside the Windows folder. 2. d/l SetDevicePath.exe and execute the command SetDevicePath.exe %WinDir%\D Just wanna know if I got this right, thanks for any replies.