89 replies to this topic

[Lancelot]

No problemo guys!

Yeah now you can use environment variables inline! I don't think that the JMicron issue is one that is because of my program though. It's most likely the driverpacks.

to avoid misunderstanding, in my normal builds:
i use same dpspack with galapo's script for LiveXP, in which jmicron connected harddisks are working nicely (as i wrote before)
also
i use same dpspack with DPs_BASE_805.exe for BartPE and Ubcdwin, in which jmicron connected harddisks are working nicely.

catch was made with jmicron drivers, but as DPs use jmicron drivers this way, than DPs probably use some other drivers with similar method which will make driverforge fail too. Hard to make catch as there is not much testers that use chipsets rather than ich..

all other info/test results are provided in previous posts.

I hope these help to improve your program with dps

[amalux]

Script updated to 4.5.2

Thanks kickarse

[kickarse]

Script updated to 4.5.2

Thanks kickarse

Thanks! v4.5.3 is out

[amalux]

Script updated to 4.5.3, keep 'em coming

Thanks kickarse! Nice new options

[kickarse]

v4.5.4 is out... fixed some issues with PNP device installs.

[amalux]

v4.5.4 is out... fixed some issues with PNP device installs.

Just got back, script updated to 4.5.4

[Lancelot]

v4.5.4 have problem when adding driver
http://img115.images...24053328nu5.png

v4.5.3 dont have such a problem with same settings
http://img518.images...55/snap1gj7.png

the driver i try to use is not from dps, it is the driver i use successfully for any x86 win os.
http://lancelot.winb...n_JMB363_32.rar

i will keep going with 4.5.3

[amalux]

Good catch! - I'll put 4.5.3 back on first post with note and hopefully kickarse can address this for next release.

[Lancelot]

Here is 10 script i wrote for DriverForge trials installing DPS drivers.
Maybe they can be written in better way, it is up to you.

Well, all scripts are not needed, etc etc. But as DPS decide to make 10 packages, i made 10 scripts for future/easy trials.
I like using this with LAN most , also graphic A works nicely (at least) too. And as driver files are in programfiles folder, it wont increase the size of .img file. .

You should download and put DPS files yourself

Amalux, I wont make a new topic for these scripts, i like all eggs in one basket, if you like you can put it in first post.

http://lancelot.winb...lot_Scripts.rar



Also here is a nice news from DPS, http://www.driverpacks.net/
With new DP_Graphics_A
Added BartPE code to .ini per Overflow request (fixed tags so unique now)

Although these are good news, I am looking forward new massstorage which will support many many new hwids

[amalux]

Thank you for this nice offering! - I may have some questions after testing.

I will update first post soon (server willing).

[Galapo]

Although these are good news, I am looking forward new massstorage which will support many many new hwids

Me too -- I just have to code it...!

[amalux]

First post updated with recommendations from Lancelot

[MedEvil]

Does Driverforge include all drivers supplied to it into Windows or just the ones, hardware is found for on the current machine?

[amalux]

Does Driverforge include all drivers supplied to it into Windows or just the ones, hardware is found for on the current machine?

Good question, I haven't tried installing drivers for non-existent hardware but it should put in whatever you supply without issue

[ludovici]

Thanks for this scripts !!!

Can you say me if your script is functional in VistaPE 12 RC1 or later. (The integration of Audio Driver is very interesting...)
Thanks for your answers

[amalux]

Thanks for this scripts !!!

Can you say me if your script is functional in VistaPE 12 RC1 or later. (The integration of Audio Driver is very interesting...)
Thanks for your answers

Sorry, missed this... I have no idea if this would work but next time I'm testing VPE I'll see what happens

[ludovici]

Sorry, missed this... I have no idea if this would work but next time I'm testing VPE I'll see what happens

Hello Amalux,

Have you test on VPE the DriverForge 4.5.4 ?

Thanks,

[amalux]

Hello Amalux,

Have you test on VPE the DriverForge 4.5.4 ?

Thanks,

Hi ludovici

I really need to check in here more often, missed this one too - sorry. I'm afraid I have not; been busy with adding portable apps in livexp. I'll run a test tonight and report back...

[amalux]

Hi ludovici

... I'll run a test tonight and report back...

OK, mixed results, the program/script works but takes 3-4x as long to finish than with same drivers in LiveXP and my wireless mouse dies in VPE during import but not affected in LiveXP. This is running VPE on an XP host (if that matters). Anyway, the program finishes successfully and the drivers get installed so I guess that means it works; the mouse issue may only affect certain wireless setups. Hope that helps

[alex7street47]

Hi, im using LiveXP,

1.how can i made my own "Driver" since i could find my plotter driver on driverpack...?
the driver only contain 1 fiile plotterDX.exe
should i install it first and back it up with backupdriver?

2.if i use backupdriver, how should i change the c:\windows\system32 on *.inf
to be compatible with liveXP /i386/system32
? any tune on *.inf that neccesary?

3. whats script (driverforge.ini)do i need to made my driver above install in stealth
after boot?
is it correct? (its gave me error)

[AutoInstall]

Automatic_Install=Y

Silent_Install=Y

Sleep_at_Start=1

Show_Device_Manager=N

Delete_Uncompressed_Drivers=Y

[Drivers]

Compressed_Driver_Location=x:\usb\plotterdrv\DXY.zip

Uncompressed_Driver_Location=C:\Drivers

[Settings]

Delete_Uncompressed_Drivers=Y

Restart_Machine=N

Show_Device_Manager=N

Check_For_Wizard_Title=Found New Hardware Wizard

Driver_Install_Method=Native

Driver_Signing_Policy_Pre=IgnoreUser

Driver_Signing_Policy_Post=Warn

[Scripts]

Pre_Script=N

Pre_Script_File=

Pre_Script_Show=

Pre_Script_Wait=

Pre_Script_Switches=

Post_Script=N

Post_Script_File=

Post_Script_Show=

Post_Script_Wait=

Post_Script_Switches=

Thanks.

[Lancelot]

alex7street47

1.how can i made my own "Driver" since i could find my plotter driver on driverpack...?
the driver only contain 1 fiile plotterDX.exe

My crystal ball is not working today and i cant see which driver you are talking about, maybe you can give more info about the mystery .... driver, provide driver files or give link etc.

does your plotter driver work with LiveXP by using either dipe or dforge with the usual methods ??????
(and god and crystal ball knows how you connect plotter, usb, com2, printer port.....)

3) Check DrvF_DPS script i wrote which creates proper automated ini files.
I am sure after post267 & 268 of dipe topics, you already have DrvF_DPS in your archive. Just check what it creates etc.

[alex7street47]

My crystal ball is not working today.

sorry for the crystal-ball, thehe. :>

its an old roland DXY - 800 on lpt1 port directly to pc with lpt1
no, Dipe and driverforge usual method cant do the job.
ill still do more research on it.

yes u re right, i have "DrvF_DPS script" ...ill go check, read it again.

q:btw. how can i check dependency of the "*.script"?
a:by reading its script or read the *.log, right?

actually, i already made them all works, but when i decide to tweaks them, here we go... ill try to figure it out.

Thanks.

[Lancelot]

no, Dipe and driverforge usual method cant do the job.

Himmm, than you say using dipe to get driver from the hostos dont work for your printer. Another mystery partly solved.
Than forget them for a while

q:btw. how can i check dependency of the "*.script"?

you cant, you can read what script need by selecting it with winbuilder

a:by reading its script or read the *.log, right?

..... they show what script is and how it processed during build......

I dont have a lpt printer (well i had loooong time ago :>), as far as i remember there were some utilities around that backs up printer driver and restores etc. Maybe they can help.

You are very mysterious alex7street47, I hope some others may help you, I wish you my best luck

[kickarse]

Hi guys! Long time no talk Hopefully this version fixes some issues that were present in the last versions.

v5 is out!

+ Fixed issues with DevicePath registry settings, will revert back to original location previous to DriverForge installation
- Removed Pre and Post scripts, users can do that with a batch and automation
- Fixed GUI wording
+ Added an option to add default Windows DevicePath to registry
+ Made all files install to Temp folder
+ Fixed edit code to delete all installed temp files

[amalux]

Script updated (DriverForge v5.0) here