You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Wim Leers
BartPE support will be added: mainly for network, mass storage and chipset drivers, but you will also be able to load graphics drivers. Loading times may indeed increase significantly if you choose to slipstream all DriverPacks.
You can indeed install the DriverPacks after Windows is installed. Search the forum for "drivers CD", "drivers disc" and check the feature requests forum. I'm still waiting for the online manual software, it's still under development.
ati3112r supports all ATI-chipset-specific SiI3112r controllers.
Did you test your workaround on a SiI3112r controller on a ATI chipset based motherboard, zorro?
These kinds of errors are always due to corrupt ISO's or corrupt CDs or DVDs, I'm afraid... Please retry with a different CD-RW or DVD-RW than the one you're currently using.
doesnt work.....
Please post your DPsFnshr.log 
Correct me if I'm wrong but I was under the impression that JBL was planning to use RIS?
It actually was a typo in the slipstream modules for method 1. It only occurred when you would disable QSC, which is why it has not been discovered until recently.
I've got some good news from you. The tools to create what you need are already available today: RogueSpear's AutoImage.
I'm already using it, but I've added support for several not supported cards myself. I've contacted Patje a long time ago about it, but he seems to keep on forgetting to add them.
The Mobility driver is broken in the last version of DriverPack Graphics B because of a type by me, not because of the Mobility Modder. Note that I don't reapply the Mobility Modder each time!
it is immposible (to post DPsFnshr.log) because i do not have that buggy laptop anymore and did not make a copy of log file
i vote for closing this topic
Kind of an odd problem, but if you ask to close it because it's somehow solved, then I'll do so. Topic closed.
I've just installed a fresh XP with hand made SVCPACK.INF (compressed as SVCPACK.IN_), and it WORKS !!
Sound card is detected and driver installer, and all works fine thanks !!
And I can tell you this problem is solved in DriverPack Sound B 6.09! No more manual editing then.
Just submitted the Danish translation to the bugtracker.
- This might be a stupid question: - Can you translate the Finisher?
-------------------------
Anders Hagen Hansen
Thanks! This will be included in the 6.09 final!
And nope you cannot. Not yet.
Does this problem still exist?
It's on hold: more important installation platforms to support first (BartPE, sysprep and RIS).
You should slipstream hotfixes (not DriverPacks) using HFSlip. After that you should apply the DriverPacks BASE.
ROE.exe is only used during cmdlines.txt to start the Finisher. The command for the removal of the %SystemDrive%\D directory is added to the registry by the DriverPacks Finisher. So it's NOT running before user logon. It's added DURING the first user logon, just before the DriverPacks Finisher has finished.
Please post your DPsFnshr.log so I can see why %SystemDrive%\D isn't deleted by the DriverPacks Finisher itself (i.e. what exception is still locking some files.)
Implemented in 6.09.
S3pHiroTh wrote:...
Ah you must restart pc for deleting the folderyeah but this thing had to be done after restart (in log i find some records about deleting DP catalog after restart, but after that catalog 'D' was in its original place)
imho problem is - i login into system with different name than the system was installed
But I am already adding it to the HKLM, not to the HKCU. So are you sure the registry entries aren't deleted by WPI for example? Or some script of your own?
Yep that should work.
If you cloned (through imaging) your Windows to the new hard drive, then it won't work. Windows will still try to load the old driver and you'll get a BSOD. There are however techniques that make it possible to transfer your Windows nevertheless, but they'll involve quite alot of work. I don't know if it would be easier for you to just make backups of all your settings and software and then reinstall it all?
If you want to configure everything yourself, you may want to try HFSlip.
Thanks for post your success story, cliche!
Bâshrat the Sneaky wrote:I doubt many people would use it. I think more people would prefer to have it DISABLED. So if you agree with me, then I'll add this as an exception to the DPsFnshr.ini so that this device will simply be removed from the system (and hence you will no longer see the not-yet-installed device in Device Manager).
Sounds fine to me
I just hate the little Yellow things in the device manager~Dave
I know the feeling I'll add it to the DPsFnshr.ini then!
Add the DriverPacks Finisher as the very LAST item to be executed by WPI then and retry.
Hi
dunno why RVM fixes svcpack coding translation, but it does.
just tried that with source from CDROM copy, with a version I knew had the issue.RVM, and then all BPs packs.
sound realtek installed OKwill look wether it has these question marks after I been to the beach
He does use the exact same method... asked Siginet myself.
Could you both (drizzle and zookeeper) post your HWIDs? Check my sig for a tool or just copy/paste a DPsFnshr.log.
DriverPacks.net Forum » Posts by Wim Leers
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.061 seconds, 5 queries executed ]