Something, Anything with pics
Screenshots will obviously be there, no matter what system will be used.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Wim Leers
Something, Anything with pics
Screenshots will obviously be there, no matter what system will be used.
I'd like to get some feedback regarding the manual I'm about to start putting together. What do you prefer?
-a .chm file
-a wiki (anonymously editable)
-a wiki (anonymously editable but with approval before allowing the changes)
-a custom website, in the style of the php.net manual
-something else
Please post your opinions! Brainstorming makes better products.
So you actually DID NOT see the warning, while expecting it? Oh ...
Then That's A Good Thing®
A better method for detecting the Windows version will be used in the future! (Thanks to RogueSpear and Siginet for all information regarding those other methods. )
Two different topics for this issue. The other one has less offtopic messages, so we'll continue the search for the cause there.
Topic closed.
So what was the problem?
Implemented now
I will add this as an option.
About which exact files does setup complain?
1. Check bug #87 in the bugtracker and this topic. Solved now
2. Known issue, will be fixed in the next version.
3. DriverPack CPU will be updated soon now. And that's NOT a bug, obviously
This rather strange problem might be solved in the next version of the DriverPacks BASE, thanks to the new DriverPacks Finisher. Please let me know.
Please post the filenames of your 3rd party DriverPacks!
I already have an error using GUI/method 1
Can track error to duplicate "D" directory created under $OEM$\$1, no files can be copied to $$ directory and program stop on Critical Error
ie: $OEM$\$1\D\D\C
Walter
That seems to be the same as this problem. As you can see it's solved now.
I have the same identical error both with Mode1 and Mode2. Also the catalyst setting is never saved! Will this be fixed in the next version?
The lack of properly saving the ATI_cpl setting is fixed in the next version, yes
@topic starter: you STILL have not posted the filenames of the 3rd party DriverPacks as I had requested. Pleae do so, else this definetely won't get solved
Whatever the exact issue was (probably it was your AV which had quarantined the file and therefore it would no longer be available), it will be solved in the next version (6.07), since cmdow.exe won't be used anymore thanks to the new DriverPacks Finisher. Bye bye batch files.
Submitted to the bugtracker: bug #87, since no one had already done so.
Fixed in 6.07: no more batch file to finish the installation, but a worthy successor: DriverPacks Finisher, with better logging output etc.
As you may have noticed, the bugtracker and the forum can be VERY slow at some moments. I've contacted the hosting's support service and they're willing to move me to a different database server. I've set it up that THEY will update the config files, which should get us the most minimal downtime possible.
I am not (yet) informed when exactly this is going to happen, but let us all hope that we won't notice it all!
My apologies for any unconvenience!
even i have the same problem....but i get 0x0000007E (0xC0000005, 0xF7509174, 0xF7CC1D44, 0xF7CC1A40)
i get this just after xp installation...that is prior to first boot...so no automated software installation..!!Regards,
MudvariP.S.:
PCI\VEN_1002&DEV_4379&SUBSYS_D6008086&REV_80\3&61AAA01&0&90 : Standard Dual Channel PCI IDE Controller PCI\VEN_1002&DEV_437A&SUBSYS_D6008086&REV_80\3&61AAA01&0&88 : Standard Dual Channel PCI IDE Controller
Please use code tags next time. What mass storage controller do you have? It seems it is not yet supported by the current DriverPacks. If you've got an a-brand pc (Dell, HP, ...) then please post the model name. If you've got a custom built pc, please post the name of the motherboard.
Of course only 3rd party DriverPacks that support the currently active platform will be slipstreamed.
Originally there was support for 3rd party DriverPacks individual selection, but in my experience users don't keep up with the strict naming system that is required, so I'd be flooded with questions 'Why doesn't my version number show up correctly?' and 'Why isn't my DP listed?'. It might be added again in the future though.
But my goal is to add all possible DriverPacks. For that, I must first automate the searching for new drivers.
It will be ready when it's ready
Eh... totally forgot about that, will look into it tomorrow. Thanks for remembering me!
EDIT: it's not INTEGRATION WITH, it's DETECTING OF, to avoid conflicts
I COULD have put it online today, but I decided not to, so I can run some tests myself tonight and tomorrow. The slipstreamer has not yet been tested AT ALL with after all these changes, and I'm quite sure there will be some major blocking bugs - which would make testing problematic .
Many unforeseen things happened today, which resulted in only 3.5 hours of time to spend on the DriverPacks... else it would have been finished by tonight.
So... one more day of patience and thy shall receive!
P.S.: I HAVE completely debugged the new GUI now Changing languages or platforms works snappy
jtdoom wrote:U verdient een pluim.
Een grote, ze kan u wat koelte toewaaien.Haha, I don't think that will suffice regarding those temperatures
But better than nothing, I guess
Nice one
The GUI framework is finished, just a few tiny bugs left to squash. Additionally, the entire structure has had some changes (mostly relocations), to make the code more maintainable, and in particular extensible: lots of new platforms (both destination OS and slipstream platforms) are to be added during the next months.
6.07.1 b1 will probably be put online tonight. Previous beta testers will automatically have access to the beta forum (and thus to the beta), others who would like to participate, please let me know here (if you're not yet registered at this forum, please do so then).
The most important things to test: the (revised) GUI (should work just fine) and the brand new DriverPacks Finisher.
P.S.: if the multiboot GUI (+internal changes) is not yet finished by tonight, then it will be in beta 2 (tomorrow most likely).
I've submitted it to the bugtracker now: BUG #84.
I think I've found the solution, but still have to test it.
Problem is, although this is a completely harmless operation it is being abused by some malware/trojans/keyloggers so it got
blacklisted.
Yep, that's the cause. It's not a virus though... just a tool to hide windows...
A shame really, because if you go that way, one had to blacklist Windows as well, as it enables these malware to execute ;P
I agree
In DriverPacks BASE 6.07, this tool won't be used anymore: the finishing script is completely rewritten. No more worthless, yet annoying virus warnings!
First, this question has been answered in the forum already.
Second, you should check the description at the bottom of the QuickStream Cache page. That's exactly why I've put it there.
Please use the search function first next time
Just to let you know... the next version will not be finished today. A couple of days later. Due to unforeseen circumstances in my life and due to the extreme weather (35 degrees Celsius in the shadow!).
It'll be worth the waiting!
It's about perfection. But it's more about supporting more installation and hardware platforms
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.072 seconds, 5 queries executed ]