[tslug]

redia, on Mar 8 2008, 03:13 PM, said:

Tslug,
are you using sysprep ? or are you deleting the drivers folders ?

Not using sysprep, using Driveforge, not deleting the drivers folder, either. Source is USB or CD, destination is folder at root of local system drive. Today I found that by modifying the registry back to the %systemroot%\INF folder, then restarting, then rediscovering hardware after removing the yellow exclamation points, it discovered them correctly. I don't know why, it seems like DriveForge maybe installed drivers for the monitor that didn't work correctly, then the default INF just made it a plug and play monitor, maybe, and that was better or something. Also, IDK why driverforge leaving the default driver folder to the uncompressed drivers means that it can't recognize things as simple as a USB key w/o changing it back to the INF folder.

Anyway, I can't really give the computer back to a client w/o switching the registry back to the INF folder, so that'll be cool when that tweak is done, IMO.

[redia]

tslug, on Mar 9 2008, 04:00 AM, said:

redia, on Mar 8 2008, 03:13 PM, said:

Tslug,
are you using sysprep ? or are you deleting the drivers folders ?

Not using sysprep, using Driveforge, not deleting the drivers folder, either. Source is USB or CD, destination is folder at root of local system drive. Today I found that by modifying the registry back to the %systemroot%\INF folder, then restarting, then rediscovering hardware after removing the yellow exclamation points, it discovered them correctly. I don't know why, it seems like DriveForge maybe installed drivers for the monitor that didn't work correctly, then the default INF just made it a plug and play monitor, maybe, and that was better or something. Also, IDK why driverforge leaving the default driver folder to the uncompressed drivers means that it can't recognize things as simple as a USB key w/o changing it back to the INF folder.

Anyway, I can't really give the computer back to a client w/o switching the registry back to the INF folder, so that'll be cool when that tweak is done, IMO.

tslug,

which version of driverforge are you using ?
kickarse is already working on solving the devicepath issue, so he will probably release it very soon. but if I am not mistaken he is also adding a couple of new improvement which could explain that the version has not been released yet.
until then you can simply script the modification in the registry
i.e.
save devicepath status
run driverforge
restore devicepath

I advise you to save/restore because in most of the cases you will have %systemroot%\inf but in some rare cases the device path might already contain different values.. so save/restore covers all cases

Cheers,
R.

[kickarse]

redia, on Mar 9 2008, 09:12 AM, said:

tslug, on Mar 9 2008, 04:00 AM, said:

redia, on Mar 8 2008, 03:13 PM, said:

Tslug,
are you using sysprep ? or are you deleting the drivers folders ?

Not using sysprep, using Driveforge, not deleting the drivers folder, either. Source is USB or CD, destination is folder at root of local system drive. Today I found that by modifying the registry back to the %systemroot%\INF folder, then restarting, then rediscovering hardware after removing the yellow exclamation points, it discovered them correctly. I don't know why, it seems like DriveForge maybe installed drivers for the monitor that didn't work correctly, then the default INF just made it a plug and play monitor, maybe, and that was better or something. Also, IDK why driverforge leaving the default driver folder to the uncompressed drivers means that it can't recognize things as simple as a USB key w/o changing it back to the INF folder.

Anyway, I can't really give the computer back to a client w/o switching the registry back to the INF folder, so that'll be cool when that tweak is done, IMO.

tslug,

which version of driverforge are you using ?
kickarse is already working on solving the devicepath issue, so he will probably release it very soon. but if I am not mistaken he is also adding a couple of new improvement which could explain that the version has not been released yet.
until then you can simply script the modification in the registry
i.e.
save devicepath status
run driverforge
restore devicepath

I advise you to save/restore because in most of the cases you will have %systemroot%\inf but in some rare cases the device path might already contain different values.. so save/restore covers all cases

Cheers,
R.

I'm definitely almost finished. I've been on hiatus, bought a house, so I've been and am quite busy at the moment. But it'll be out soon

[Kingskawn]

Hi

I've got an unattented installation sysprepped machine. The thing I want to do is at the end of the installation procedure call the .inf that will do a last hardware installation. This have to be automatic without any user interaction.
I already made an .inf. I don't know if it's correct but I looked on the 'manual'. Can you tell me if I'm correct?
I will work with the Driverpacks that are in 7z format and it must delete drivers when it finishes.

[AutoInstall]
UnAttended=Y
AutoCheck7zLoc=N
DeleteUncompressedDrivers=Y
RestartMachine=N
ShowDevMgr=N
VerySilent=Y
Sleep_at_Start=1

[Driver]
7zRoot=N
7zRootLoc=C:\temp\compressed <--- folder where the 7z's from Driverpacks are
DriverRoot=N  <--- doesn't really understand the meaning of this
DriverRootLoc=C:\Windows\Drv <--- Folder that already exists and where I've put several drivers
DriverExtract=C:\Windows\driverforge <--- Location where driverpacks will be uncompressed
7zLoc=C:\temp\compressed <--- folder where the 7z's from Driverpacks are
Use_System_Root_INF=N

[Misc]
CheckForWizardTitle=Found New Hardware Wizard <--- can add some more, things that are new
Delete_Existing_Driver_Log=N

Will that autorun.inf executes at the end of a script or do I need an .exe?

This post has been edited by Kingskawn: 11 March 2008 - 03:46 AM

[Kingskawn]

Kickarse or anybody?

[kickarse]

Kingskawn, on Mar 12 2008, 03:26 AM, said:

Kickarse or anybody?

Sorry i've been out of touch with the internet.

I'll get to this tomorrow. I'm off to sleep.

[kickarse]

v 4.1.2 (more of an interim to more gui changes) out!

[Sull]

This looks very neat, this should work perfect for a project of mine.

Question = when the ini file is filled out properly for unattended, just running DriverForge.v.4.1.2.exe will automatically install the drivers, no switches are needed ?

Thanks I will test soon.

EDIT:

can I use this

DriverExtract=%SYSTEMDRIVE%\

instead of this

DriverExtract=C:\

This post has been edited by Sull: 04 April 2008 - 07:58 PM

[kickarse]

Sull, on Apr 4 2008, 08:43 PM, said:

This looks very neat, this should work perfect for a project of mine.

Question = when the ini file is filled out properly for unattended, just running DriverForge.v.4.1.2.exe will automatically install the drivers, no switches are needed ?

Thanks I will test soon.

EDIT:

can I use this

DriverExtract=%SYSTEMDRIVE%\

instead of this

DriverExtract=C:\

That should work. Or you could try @systemdrive . And yes to your first question.

[iTwins]

Great idea and a great tool!! Kudos. Kickarse!

One problem though:

I noticed that if I extracted USB drivers into C:\DRIVERS for example, detected and installed all drivers, and finally deleted C:\DRIVERS permanently. The next time I insert a USB thumbdrive/hdd, the system will not be able to find the drivers it needs, not even USB drivers that originally came with XP. I believe the tool may have changed the search path and points to C:\DRIVERS instead. Because of this, I normally extract the drivers deep inside "%SystemDirectory%\Driverforge" and let them be just in case...

I tested not from the latest version but several revisions back, so I am not sure if this has since been fixed already or not.

Cheers,

[Sull]

kickarse,

Quote

Or you could try @systemdrive

Your saying with @, I am not sure if it was doing anything with %SYSTEMDRIVE%\ I was just testing in VMWARE so I cant really say much until I try actually install on my MicroPC.. I just want to limit the amount of times I have to test it.

[kickarse]

iTwins, on Apr 7 2008, 01:17 AM, said:

Great idea and a great tool!! Kudos. Kickarse!

One problem though:

I noticed that if I extracted USB drivers into C:\DRIVERS for example, detected and installed all drivers, and finally deleted C:\DRIVERS permanently. The next time I insert a USB thumbdrive/hdd, the system will not be able to find the drivers it needs, not even USB drivers that originally came with XP. I believe the tool may have changed the search path and points to C:\DRIVERS instead. Because of this, I normally extract the drivers deep inside "%SystemDirectory%\Driverforge" and let them be just in case...

I tested not from the latest version but several revisions back, so I am not sure if this has since been fixed already or not.

Cheers,

Yeah I fixed that issue. If you select to delete drivers then it'll revert it back to whatever was there before.

[Sull]

I do have another question.

Can this be ran from RunOnceEx without problems ?

[kickarse]

Sull, on Apr 8 2008, 01:32 AM, said:

I do have another question.

Can this be ran from RunOnceEx without problems ?

I don't see why not, it should work fine.

This post has been edited by kickarse: 08 April 2008 - 07:18 AM

[Kelsenellenelvian]

KK I'm going to play the dumbarse noob now.

I want to use this as a all-in-one CD not from usb.

#1 The drivers are staying compressed on the CD.

#2 I want them extracted to %SYSTEMROOT%\Drivers

#3 They can be deleted aftaerwards.

#4 I wold like to see the hardware manager during the proccess.

As far as I have read a variable will work fine for the extraction but how do I denote a %cdrom% variable?

Or just me being lazy can someone post me an ini file?

[kickarse]

Kelsenellenelvian, on Apr 12 2008, 10:43 PM, said:

KK I'm going to play the dumbarse noob now.

I want to use this as a all-in-one CD not from usb.

#1 The drivers are staying compressed on the CD.

#2 I want them extracted to %SYSTEMROOT%\Drivers

#3 They can be deleted aftaerwards.

#4 I wold like to see the hardware manager during the proccess.

As far as I have read a variable will work fine for the extraction but how do I denote a %cdrom% variable?

Or just me being lazy can someone post me an ini file?

Just use the options

[AutoInstall]
ShowDevMgr=Y

[Driver]
7zRoot=Y
7zRootLoc=Path\To\Driver\Folder
...
DriverExtract=%systemroot%\Drivers
7zLoc=

I would suggest that if you're going to delete the drivers that you put them in a folder other than %systemroot%\INF . Because it'll delete the folder %systemroot%\inf . The program would be on the CD-Rom and the folder for the compressed drivers would be in a the same folder as the program.

So %cdrom%\DriverForge\DriverForge.v4.1.2.exe
and %cdrom%\DriverForge\CompressedDriversFolder

I have to redo the drivers location approach. It's a bit convoluted and confusing. Soon it'll be just 7zRoot and 7zLoc, and DriverRoot and DriverExtract, nixing 7zRootloc and DriverRootLoc.

[slipk487]

its easy. this is what you have to do.

it doesnt matter were u have your files on a cd but the easyest way is to have your drivers in a subfolder in the directory were u have DriverForge.exe

lets say this is your setup

X:\DriverForge\DriverForge.exe
X:\DriverForge\Drivers\(anything in here or subfolders deeper)

you directory would just be \Drivers


Question of my Own.
Does this work on windows 2000 because when i try in run it on Windows 2000 i get some kind of error after i hit start.

This post has been edited by slipk487: 16 April 2008 - 02:26 PM

[kickarse]

slipk487, on Apr 16 2008, 03:24 PM, said:

its easy. this is what you have to do.

it doesnt matter were u have your files on a cd but the easyest way is to have your drivers in a subfolder in the directory were u have DriverForge.exe

lets say this is your setup

X:\DriverForge\DriverForge.exe
X:\DriverForge\Drivers\(anything in here or subfolders deeper)

you directory would just be \Drivers


Question of my Own.
Does this work on windows 2000 because when i try in run it on Windows 2000 i get some kind of error after i hit start.

I've only tested in XP. I don't know if it'll work on 2000. Can you print screen the error??

[slipk487]

ill post it tomorrow when im back at work

edit.
didnt work today so ill post the error on monday

This post has been edited by slipk487: 18 April 2008 - 12:55 PM

[slipk487]

sorry it took so long to get to. I've been busy at work and haven't had a change before to test the error again but i have the error now. it happens during the installing drivers portion.

Attached File(s)

•  DriverForge_Error.jpg (15.25K)
  Number of downloads: 3

This post has been edited by slipk487: 14 May 2008 - 12:27 PM