[kickarse]

slipk487, on May 14 2008, 02:26 PM, said:

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.

Can you search your computer for the file syssetup.dll and let me know it's full path?? And possibly send me your 2k version of the syssetup.dll file?

This post has been edited by kickarse: 15 May 2008 - 03:59 PM

[slipk487]

just now seen the post. problem is i graduated and no longer work at my school. its just a standard win2k with sp4.

[darkleon]

wow your work is awesoming,
now,it is that i understand.
If i had mountains of drivers that Driverspacks, i can use it, to search for the correct driver for the machine?
let me know if its rigth
...
lol its great.
thanks.

[rogergh]

Would like to inform you that version 4.1.2 created some kind of bug that made the driverinstallation fail on any norwegian XP version (english worked).
Version 4.0 works on the norwegian version without any problems.

The problem must be in the driver-install phase, since the extraction of the driver-files work fine, but I'm not sure if driverpack can find the drivers after extraction.

This is the .ini I use with Driverforge 4.0:

[AutoInstall]
UnAttended=Y
AutoCheck7zLoc=Y
DeleteUncompressedDrivers=Y
RestartMachine=N
ShowDevMgr=N
VerySilent=N
Sleep_at_Start=1
[Driver]
7zRoot=N
7zRootLoc=
DriverRoot=N
DriverRootLoc=
Use_System_Root_INF=Y
7zLoc=C:\Diverse\Drivere\Drivere
DriverExtract=C:\Diverse\Drivere\Ukomprimert
[Misc]
CheckForWizardTitle=Veiviser for funnet maskinvare
Delete_Existing_Driver_Log=Y


The only difference I could see from 4.0 -> 4.1.2 is that the line "Use_System_Root_INF=Y" was removed.
Could you check the changes between those two versions to see if anything you did could have cause this bug?
Any suggestions?

[Avneet]

will this work from a dvd/cd .. if all the drivers and this app are on a dvd/cd

[Avneet]

hi am having a problem ...

i was just testing this locally on a machine.. i uinstalled a few drivers and ran this app.. i chose the compressed driver location and the path to extract it too.. well extraction takes time and everything went fine.. the misisng drivers were installed.. but i want to avoid the extraction process.. so i want to put all the extracted drivers in a folder.. so wat changes to do i need to make in the ini file..please help

thanks

[estecb]

I'm sorry if my question is already replied.

this support Windows XP x64??

If it isn't , what application I can use to sliptream my SATA drivers?.

Thank's in advanced.
Take care

This post has been edited by estecb: 18 July 2008 - 06:43 PM

[kickarse]

Avneet, on Jun 10 2008, 10:36 PM, said:

hi am having a problem ...

i was just testing this locally on a machine.. i uinstalled a few drivers and ran this app.. i chose the compressed driver location and the path to extract it too.. well extraction takes time and everything went fine.. the misisng drivers were installed.. but i want to avoid the extraction process.. so i want to put all the extracted drivers in a folder.. so wat changes to do i need to make in the ini file..please help

thanks

Ahh, I'm not sure why but I'm planning on rewriting the driver import/scanning function instead of using a third party tool.

estecb, on Jul 18 2008, 08:41 PM, said:

I'm sorry if my question is already replied.

this support Windows XP x64??

If it isn't , what application I can use to sliptream my SATA drivers?.

Thank's in advanced.
Take care

The program won't allow you to slipstream your drivers onto a cd. You can use nlite for that though. Or bashrat's driverpacks.

[kickarse]

v4.3 is up and available for download. It has an internal driver import function now. So hopefully no errors!

[kickarse]

v4.4 is up! It's easier to setup and less convoluted.

[amalux]

Hi kickarse! Having some issues with 4.4 (possibly download corruption); noticed last night the 'header art' was missing
 df44.JPG (27.71K)
Number of downloads: 13
(still pretty but needs a bit of makeup )

Tried new downloads but now .exe corrupted

Time for another update?

EDIT: Sorry, problem on my end, will have to TS - Ignore above!

This post has been edited by amalux: 27 July 2008 - 09:09 AM

[kickarse]

amalux, on Jul 27 2008, 10:59 AM, said:

Hi kickarse! Having some issues with 4.4 (possibly download corruption); noticed last night the 'header art' was missing
df44.JPG
(still pretty but needs a bit of makeup )

Tried new downloads but now .exe corrupted

Time for another update?

EDIT: Sorry, problem on my end, will have to TS - Ignore above!

Phew! Are you going to re-screenshot for boot-land?

[amalux]

kickarse, on Jul 27 2008, 08:29 AM, said:

amalux, on Jul 27 2008, 10:59 AM, said:

Hi kickarse! Having some issues with 4.4 (possibly download corruption); noticed last night the 'header art' was missing
df44.JPG
(still pretty but needs a bit of makeup )

Tried new downloads but now .exe corrupted

Time for another update?

EDIT: Sorry, problem on my end, will have to TS - Ignore above!

Phew! Are you going to re-screenshot for boot-land?

Well, we're not out of the woods yet; there seems to something missing in v.4.3 and 4.4 that causes this odd behavior. I have to go back and re-install v.4.1.2 (last version I have before 4.3) to get missing functionality and then 4.3 and 4.4 work fine! Does this make sense to you?

[Lancelot_Real]

hi kickarse,
nice work,
v4.4 worked nice for me i will try old versions too, i wrote sth here maybe/maybenot you get interested.
http://www.boot-land.net/forums/index.php?...ost&p=40541

only one question, is there a plan of making command parameter to DriverForge beside driverforge.ini file?
example: cmd: DriverForge D:\dpsdrivers %systemroot%\system32\drivers ............

[kickarse]

Lancelot_Real, on Jul 27 2008, 04:31 PM, said:

hi kickarse,
nice work,
v4.4 worked nice for me i will try old versions too, i wrote sth here maybe/maybenot you get interested.
http://www.boot-land.net/forums/index.php?...ost&p=40541

only one question, is there a plan of making command parameter to DriverForge beside driverforge.ini file?
example: cmd: DriverForge D:\dpsdrivers %systemroot%\system32\drivers ............

Possibly at some point. But I wanted to make sure it worked first before I added additional functionality. I updated the post at boot-land.

Is it just the image Amalux?

This post has been edited by kickarse: 27 July 2008 - 03:19 PM

[amalux]

kickarse, on Jul 27 2008, 02:17 PM, said:

Is it just the image Amalux?

AFAIK but haven't fully tested; at times, dbl-clicking the .exe wouldn't produce a ui but I can't reproduce that now. Again, the only way (for others) to test this is if they have never had any earlier version installed. If installing 4.3 or 4.4 they get an image in the ui, then something else is at work here. I test this by restoring my HDD to a point previous to any DF install

This post has been edited by amalux: 27 July 2008 - 04:08 PM

[Lancelot_Real]

kickarse, on Jul 27 2008, 11:12 PM, said:

Perhaps I can integrate the Hwpnp utility for PE type installs?? Does anyone have a link to this?

Ed. Never mind I found it... I hope it's ok with Paraglider...

I'm going to write my app to use this program instead. Not only does it make my program faster but it also makes it smaller. We'll see I guess.

I decide it is better to write here.

as far as i understand,
* amulux wrote things to add driver to the existing os on harddisk by using pe environment with DriverForge.
* I do things to add driver to the existing pe in the pe environment with DriverForge.

NO need to add hwpnp to your app for pe, and there can be other utilites/methods to search and add device to different "pe1 os"'s (ex: in livexp there is no hwpnp but livexp already searchs for hardware and add if needed (i am new with livexp, i dont know how yet)).

But maybe you can use hwpnp to search for undefined drivers and add only the required files to os (as an option)???
example: DriverForge extract or look in and take hwids maybe in the drivers, hwpnp search for needed drivers in the environment, Driver forge extract only the needed ones.

i still have tests/trials, i wrote my foundings in bootland 'cause i couldnt make it work with the way i use using livexp yet.


amulux:
i had no problems in using driverforge4.4 in my os, also i tried on vmware/xp32 to make first time test, and it worked immediately.
But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

[amalux]

Lancelot_Real, on Jul 27 2008, 03:36 PM, said:

amulux:
i had no problems in using driverforge4.4 in my os, also i tried on vmware/xp32 to make first time test, and it worked immediately.

Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?

Lancelot_Real, on Jul 27 2008, 03:36 PM, said:

But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

kickarse is working on a new update to address these issues and add additional options

This post has been edited by amalux: 28 July 2008 - 11:21 AM

[Lancelot_Real]

amalux, on Jul 28 2008, 07:19 PM, said:

Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?

Lancelot_Real, on Jul 27 2008, 03:36 PM, said:

But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

kickarse is working on a new update to address these issues and add additional options

no i had never used or uninstalled DF install, v44 is the first one i use.

But here is a funny thing, before posting this message, i doubleclick on driverforge.exe again and vala, it didnt open. (tried many times with double clicking DriverForge.exe)
i put it in E:\1 folder with a name DriverForge.exe, and no it didnt open.
i also observed taskmanager, in taskm, DriverForge.exe shows up for a second (or less) and disappears.
BUT
as my main purpose is using this utility in livexp/bartpe, there never a problem like that yet. (i made many many test with them), this only happens when using my os. Maybe this bugy is about 2003x64 i am using so sometimes it works in 2003x64 and sometimes it doesnt work. (ps: i know this is not for x64 environment, i double click it just to see gui)

if i find a method to reproduce the problem, i will inform.

hahaha, at the end of this message, before i press send, i double click on DriverForge.exe and it started (driverforge.ini was deleted in previous trials) .
for a solution lets say, if it doesnt start, delete driverforge.ini (maybe not necessary) and deal with other things for a while, than try to start DriverForge.exe again.

[kickarse]

Lancelot_Real, on Jul 28 2008, 01:57 PM, said:

amalux, on Jul 28 2008, 07:19 PM, said:

Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?

Lancelot_Real, on Jul 27 2008, 03:36 PM, said:

But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

kickarse is working on a new update to address these issues and add additional options

no i had never used or uninstalled DF install, v44 is the first one i use.

But here is a funny thing, before posting this message, i doubleclick on driverforge.exe again and vala, it didnt open. (tried many times with double clicking DriverForge.exe)
i put it in E:\1 folder with a name DriverForge.exe, and no it didnt open.
i also observed taskmanager, in taskm, DriverForge.exe shows up for a second (or less) and disappears.
BUT
as my main purpose is using this utility in livexp/bartpe, there never a problem like that yet. (i made many many test with them), this only happens when using my os. Maybe this bugy is about 2003x64 i am using so sometimes it works in 2003x64 and sometimes it doesnt work. (ps: i know this is not for x64 environment, i double click it just to see gui)

if i find a method to reproduce the problem, i will inform.

hahaha, at the end of this message, before i press send, i double click on DriverForge.exe and it started (driverforge.ini was deleted in previous trials) .
for a solution lets say, if it doesnt start, delete driverforge.ini (maybe not necessary) and deal with other things for a while, than try to start DriverForge.exe again.

Every once in a while it doesn't unload itself properly from memory and I don't know why. Amalux has the link to the new test version. If you want it Lance let me know. I haven't tested in x64 or 2003 so I'm unsure as to what processes are crashing. We'll see if I can change this error checking code I have that checks to see if it's already running. That seems to have been the issue in previous versions with it not starting up again.

A couple things 7zLoc and DriverExtract are now called Compressed_Driver_Location and Uncompressed_Driver_Location, so 7zloc and Driverextract won't work in versions coming. Both can use CD\ to specify the current folder DriverForge is being run from. The Uncompressed_Driver_Location can use option None to specify no driverpacks.

The new option is to use Windows native installation process using syssetup.dll or use HWPNP. It's possible I have a HWPnP command line error. Update_All_Hardware is now Use_Windows_Method_For_Driver_Install, setting Y or N.

I'm working on v4.4.4 so I'll turn that error checking off. I've also updated the changelog.