I second that request.

Didn't even know 1.43 was out already.
Included 1.42 in my current CD and that came out very shortly after 1.41

Massive Month of Updates at Realtek or what? wink

Uhm, I hate to spoil it for you, but the issue is NOT fixed in 6.08.1!

Just finished installing (well, still running, but the Finisher is done - don't ask why I'm doing this so late, I started in the afternoon and went somewhere else, believing it would work "unattended"...) and I had all those issues describen in the initial post.
I had to manually exit at least five command windows, got some Voodoo Fixer stuff installed as well as some Microsoft audio programm that was never executed before and this system does NOT have HDA.

Also, as I reported previously, the last three or so RCs were fine for me, apart from DPsFnshr.EXE not getting deleted (which I couldn't care less about actually).

So, Bâshrat the Sneaky, please have a look into this, something serious must have broken on the way from last RC to final hmm


EDIT:

Finished now, here's some addendum:
* ATi CCC got installed again!
Gah, this one's killing me (thankfully my two main machines would use it actually, but still...). And that while it worked fine in last RC.
* Some "512i Digital control panel" got installed. No idea what that is...
*First time ever DPsFnshr.EXE got deleted, YAY!

Other than that, the log file:

2006-08-12 20:05:34 : <INIT> DriverPacks Finisher lastBuild initialized.
2006-08-12 20:05:34 : <INIT> Detected platform wnt5_x86-32.
2006-08-12 20:05:34 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-08-12 20:05:34 : <INIT> 1. ACPI devices

ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI-Schalter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_8\_0                 : Intel(r) Pentium(r)III processor
ACPI\PNP0000\4&80CD973&0                                    : Programmierbarer Interruptcontroller
ACPI\PNP0100\4&80CD973&0                                    : Systemzeitgeber
ACPI\PNP0200\4&80CD973&0                                    : DMA-Controller
ACPI\PNP0303\4&80CD973&0                                    : Logitech PS/2 Keyboard (106 Keys Ctrl+Caps)
ACPI\PNP0401\4&80CD973&0                                    : ECP-Druckeranschluss (LPT1)
ACPI\PNP0501\1                                              : Kommunikationsanschluss (COM1)
ACPI\PNP0501\2                                              : Kommunikationsanschluss (COM2)
ACPI\PNP0700\4&80CD973&0                                    : Standard-Diskettenlaufwerkcontroller
ACPI\PNP0800\4&80CD973&0                                    : Systemlautsprecher
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI-Bus
ACPI\PNP0B00\4&80CD973&0                                    : System CMOS/Echtzeituhr
ACPI\PNP0C01\2&DABA3FF&0                                    : Systemplatine
ACPI\PNP0C02\1                                              : Hauptplatinenressourcen
ACPI\PNP0C04\4&80CD973&0                                    : Numerischer Coprozessor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI-Einschaltknopf
ACPI\PNP0F13\4&80CD973&0                                    : Logitech-compatible Mouse PS/2
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-konformes System
ROOT\ACPI_HAL\0000                                          : ACPI-PC (Advanced Configuration and Power Interface)
20 matching device(s) found.

2006-08-12 20:05:35 : <INIT> 2. PCI devices

PCI\VEN_10DE&DEV_0110&SUBSYS_00000000&REV_B2\4&9FD38EF&0&0008: NVIDIA GeForce2 MX/MX 400
PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\3&61AAA01&0&80 : Realtek RTL8139/810x Family Fast Ethernet NIC #2
PCI\VEN_10EC&DEV_8139&SUBSYS_81391186&REV_10\3&61AAA01&0&70 : Realtek RTL8139/810x Family Fast Ethernet NIC
PCI\VEN_1106&DEV_0571&SUBSYS_00000000&REV_06\3&61AAA01&0&39 : VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_0596&SUBSYS_00000000&REV_12\3&61AAA01&0&38 : VIA PCI-zu-ISA-Brücke
PCI\VEN_1106&DEV_0691&SUBSYS_00000000&REV_44\3&61AAA01&0&00 : VIA CPU-zu-PCI-Brücke
PCI\VEN_1106&DEV_3038&SUBSYS_12340925&REV_08\3&61AAA01&0&3A : VIA Rev 5 oder höher USB universeller Hostcontroller
PCI\VEN_1106&DEV_3050&SUBSYS_00000000&REV_20\3&61AAA01&0&3B : VIA Energieverwaltungscontroller
PCI\VEN_1106&DEV_8598&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : VIA CPU to AGP Controller
PCI\VEN_1274&DEV_1371&SUBSYS_40021462&REV_08\3&61AAA01&0&A0 : SB PCI(WDM)
10 matching device(s) found.

2006-08-12 20:05:35 : <INIT> 3. HDAUDIO devices

No matching devices found.

2006-08-12 20:05:35 : <INIT> 4. USB devices

USB\ROOT_HUB\4&2301DA04&0                                   : USB-Root-Hub
1 matching device(s) found.

2006-08-12 20:05:35 : <INIT> Logging of HWIDs complete.
2006-08-12 20:05:35 : <INIT> Processed settings.
2006-08-12 20:05:36 : <FLTR> Collected the HWIDs for this system.
2006-08-12 20:05:36 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0001__D-G-A-1] (1/20).
2006-08-12 20:05:36 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-08-12 20:05:36 : <FLTR> 		Found tagfile "C:\ATICCC.ins" (1/1).
2006-08-12 20:05:36 : <FLTR> 	4. +infFiles (ANY +infFiles must matched
2006-08-12 20:05:36 : <FLTR> 		Wildcard specified for +infFiles requirement: scan for .inf files.
2006-08-12 20:05:36 : <FLTR> 		Checking .inf file "C:\D\G\A\1\C2_34826.inf".
2006-08-12 20:06:16 : <FLTR> 		Checking .inf file "C:\D\G\A\1\CX_34826.inf".
2006-08-12 20:07:14 : <FLTR> 		Checking .inf file "C:\D\G\A\1\E2_34826.inf".
2006-08-12 20:07:21 : <FLTR> 		Checking .inf file "C:\D\G\A\1\EX_34826.inf".
2006-08-12 20:07:29 : <FLTR> 		Checking .inf file "C:\D\G\A\1\MX_34826.inf".
2006-08-12 20:07:47 : <FLTR> Finished filtering exceptions.
2006-08-12 20:12:04 : <EXEC> Executed all commands (3) for exception [wnt5_x86-32__0001__D-G-A-1].
2006-08-12 20:12:21 : <EXEC> Executed all commands (2) for exception [wnt5_x86-32__0002__D-G-A-1].
2006-08-12 20:13:59 : <EXEC> Executed all commands (3) for exception [wnt5_x86-32__0003__D-G-A-3].
2006-08-12 20:14:07 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0004__D-G-3-1].
2006-08-12 20:15:08 : <EXEC> Executed all commands (3) for exception [wnt5_x86-32__0005__D-G-S-1].
2006-08-12 20:15:08 : <EXEC> Executed all commands (2) for exception [wnt5_x86-32__0006__D-L-NV-123].
2006-08-12 20:16:03 : <EXEC> Executed all commands (19) for exception [wnt5_x86-32__0007__D-S-CR-1].
2006-08-12 20:16:14 : <EXEC> Executed all commands (19) for exception [wnt5_x86-32__0008__D-S-CR-2].
2006-08-12 20:17:02 : <EXEC> Executed all commands (19) for exception [wnt5_x86-32__0009__D-S-CR-3].
2006-08-12 20:17:03 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0010__D-S-H-2].
2006-08-12 20:17:12 : <EXEC> Executed all commands (3) for exception [wnt5_x86-32__0011__D-S-N].
2006-08-12 20:17:14 : <EXEC> Executed all commands (6) for exception [wnt5_x86-32__0012__D-S-S-U].
2006-08-12 20:17:14 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0013__D-S-SI-1].
2006-08-12 20:17:14 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0014__D-S-SI-2].
2006-08-12 20:17:20 : <EXEC> Executed all commands (3) for exception [wnt5_x86-32__0015__D-S-T-2].
2006-08-12 20:17:20 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0016__D-S-T-3].
2006-08-12 20:17:21 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0017__D-S-T-4].
2006-08-12 20:17:21 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0018__D-S-T-5].
2006-08-12 20:17:30 : <EXEC> Executed all commands (1) for exception [wnt5_x86-32__0019__D-S-V-1].
2006-08-12 20:17:32 : <EXEC> Executed all commands (2) for exception [wnt5_x86-32__0020__D-S-V-2].
2006-08-12 20:29:13 : <ERR>  Could not delete the DriverPacks, which are located in 'C:\D'.
2006-08-12 20:29:18 : <CLNP> Deleted 'C:\hwids.dat'!
2006-08-12 20:29:18 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-08-12 20:29:18 : <CLNP> Deleted 'C:\devcon.exe'!
2006-08-12 20:29:18 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-08-12 20:29:18 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-08-12 20:29:19 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-08-12 20:29:19 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-08-12 20:29:19 : Program terminated.

HWIDs, just in case:

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_10DE&DEV_0110&SUBSYS_00000000&REV_B2\4&9FD38EF&0&0008: NVIDIA GeForce2 MX/MX 400
PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\3&61AAA01&0&80 : Realtek RTL8139/810x Family Fast Ethernet NIC #2
PCI\VEN_10EC&DEV_8139&SUBSYS_81391186&REV_10\3&61AAA01&0&70 : Realtek RTL8139/810x Family Fast Ethernet NIC
PCI\VEN_1106&DEV_0571&SUBSYS_00000000&REV_06\3&61AAA01&0&39 : VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_0596&SUBSYS_00000000&REV_12\3&61AAA01&0&38 : VIA PCI-zu-ISA-Brücke
PCI\VEN_1106&DEV_0691&SUBSYS_00000000&REV_44\3&61AAA01&0&00 : VIA CPU-zu-PCI-Brücke
PCI\VEN_1106&DEV_3038&SUBSYS_12340925&REV_08\3&61AAA01&0&3A : VIA Rev 5 oder höher USB universeller Hostcontroller
PCI\VEN_1106&DEV_3050&SUBSYS_00000000&REV_20\3&61AAA01&0&3B : VIA Energieverwaltungscontroller
PCI\VEN_1106&DEV_8598&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : VIA CPU to AGP Controller
PCI\VEN_1274&DEV_1371&SUBSYS_40021462&REV_08\3&61AAA01&0&A0 : SB PCI(WDM)
10 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&2301DA04&0                                   : USB-Root-Hub
1 matching device(s) found.

1,303

(3 replies, posted in Other)

Bâshrat the Sneaky wrote:

P.S.: I wish we had trees like that here... and especially the climate that's necessary for them.

Wasn't it hot enough around here the last couple of weeks? wink

Granted, I'm not too fond of the current situation either, but if kept that hot a little longer, I'm sure we could have grown some palms over here big_smile


Don't they have them in Southern Ireland?
Gulf stream and all...

1,304

(1 replies, posted in Site & Forum Issues And Feedback)

Dunno what your problem is exactly, but IE is not giving me any troubles, just FYI.

1,305

(14 replies, posted in Other)

One more:

http://www.heise.de/newsticker/meldung/76730

So we know who is to blame, eh? wink


Getting the same here.
Worked perfectly fine throughout the whoile beta phase though...
*ponders*

Same as for maxximum:

You need to fill out a report at the bugtracker as desribed here: http://forum.driverpacks.net/viewtopic.php?id=293

There, you can also attach your file so you won't have to use your "own" webspace.

Please consider, before Bâshrat the Sneaky gets mad ;P

You need to fill out a report at the bugtracker as desribed here: http://forum.driverpacks.net/viewtopic.php?id=293

There, you can also attach your file so you won't have to use your "own" webspace.

Please consider, before Bâshrat the Sneaky gets mad ;P

Bâshrat the Sneaky wrote:

Lots of respect for you, poor ME user.... Been there, done that. Could not reproduce it for you though. My only suggestion is that you use a different OS, lol. (It's also possible that the CLI version of 7zip does not work as expected when executed in Windows ME...)

Oh dear!

If I was given the choice between 98SE and ME, I'd take 98SE any day over ME.

Back then, I was using both, and I can't say I was too fond of either (boy was I glad when 2k came out!).
However, I still have a 98SE CD, while I trashed the ME one.
That gotta tell you, eh? wink

As it happens to be, I just installed 98SE on Virtual PC.
And although the "hardware" comes straight form MS so to speak, I still managed to get a rundll error straight after first boot as well as an exception handling when opening IE for the first time.
Also, trying to update to IE 6 gave me an error message before it would work after some retries.

If that doesn't tell you something IDK what will...

Suffice to say support from MSFT has ended by July 11th or so, meaning that no security updates will ever be released.
Going online with that thing (while not running in a virtual environment) is just begging for problems!


PS: In case you wonder why I'm doing this:
A cousin of mine has problems running some older games on XP and after fiddling around with the compatibility settings for a good 15min I decided this was the easier way to go - and so it looks!

coucou wrote:

What do you recommand about KTD, enable or disable???

That entirely depends on two things:
* Whether you have the HDD space to spare
and
* Whether you plan to change the hardware of the system often

If the latter is the case, then you should enable KTD, if not and you want to save some space, then disable KTD.

AFAIK it does not have any influence on the unattended installation at all.

It's just for afterwards maintenance, so to speak. smile

Here it is, all entered in the bugtracker, just as desired (I hope wink):

does this work?



EDIT: Kind of annoying, that, whenever you use the word bugtracker it auto-transforms it into the URL, breaking any URLs containing the word...

Ok, updated all links in the wiki to the respective DriverPacks I uploaded earlier.

@ Bâshrat the Sneaky:

In your intial post, the example path you gave is incorrect.
It need to be like this:

http://3rdpartydriverpacks.thesneaky.com/wnt5_x86-32/<DP name>.7z

You (or someone else) obviously moved all the packs from .\downloads to the other folder and deleted the former (or renamed or whatever).
Please update smile

Gah!

I will reupload them, in that case.

XYZ is outdated anyway by now (and sort of totally unofficial...).



EDIT:
Try again now, please.
Re-uploaded Monitor and updated XYZ (in case you want to use that).

But could you just search through them as easily as if they were extracted?
I think not since you always have to point to the *.INF file.

Or is this handled automatically (ie the path is known to Win and it will search there, just as it does with its own driver.cab)?
I never used KTD, so I wouldn't know...

No, I'm not disagreeing with making it mandatory, I can clearly see the need.
However, by doing so you at least need to tell people how to make it work wink

Thanks for the link, RS, should be included in the instructions, IMO.

Since you closed the other sticky (http://forum.driverpacks.net/viewtopic.php?id=392), I'm posting this in here *ahem*

Anyway, since the MD5 checksum is mandatory (as it was not in italics), you might also want to include a guide how to obtain the checksum using a Win System.
I'm sure there's a lot of users not knowing how to and the only thing I know about it is that it is not possible to do so without 3rd party software.

1,318

(14 replies, posted in Other)

And another update:

http://www.heise.de/newsticker/meldung/76461

Bâshrat the Sneaky wrote:
orei wrote:
Bâshrat the Sneaky wrote:

How did you manage to edit your topic and topic title?

ahahaha Bâshrat the Sneaky..
simple.. i've delete the old topic.. and wrote a new topic.. simpleeee!!! big_smile:D

bye and thanks a lot!!!

Even worse... how did you do that? yikes

Quite simple, click on DELETE on your first post.
And gonzo...

Since we can't edit the titles, this is the best way to keep tghe forum somewhat clean and orderly, seeing as I alone had some seven language file releases already.

And posting them in subsequent posts in the same thread is a bad idea, too, since the title is still wrong and you might not easily catch there's a new version.

Hm, just a wild guess but maybe try a directory/path without spaces.
This is known to cause all kinds of trouble...

While this shows us there doesn't seem to be a defect that easily lets the RAM fail (I once tested one stick that would produce errors in a row faster than you could count them!), if you really want to make sure, you should at least run the test for 24 hours.

muiz3 wrote:

I also checked the ftp site and saw what i was afraid of.
A mess , all things togheter in one folder.
No changelogs etc.

I just uploaded all the files I got from the 3rd Party wiki to the /downloads folder, just as Bâsh said.

i also saw two packs wich are new i gues with no info :
DP_WB_wnt5_x86-32_1.0.7z  contains creative cam drivers???
DP_XYZ_wnt5_x86-32.7z  all things that are already in bashrats driverpacks ...why????

Yes, the WB is indeedx the WebCam pack.
Don't ask me why it's named that way, I didn't change anything.

XYZ is a pack I created because at that time, the official DriverPacks did not contain those drivers or at least in the updated versions.
This is more or less my private pack, which I accidentially uploaded.

I will take it down once the official packs have been updated.

And put the changelog and other info in each folder to
Also when packs are not tested , why not  put them in a beta pack folder.

That would be the ideal situation, I agree.
As I said, I only uploaded them, I didn't even create them and for most of the packs didn't change them either.

Something to do for the original authors, I guess.

Anyway, most of the packs need an overhaul anyway, IMO, as the file structure is rather messy.

And when everyone has acces to this ftp its getting a mess ,now i never know if its the same or the right pack.

That could happen, but then again, I don't see the difference to the wiki, where everyone could also edit at will.

I thought there is no webcam driver available (as well as for BlueTooth) becazse every review I read of XP on Mac states those device do not work.
Last thing I heared was that Apple updated BootCamp so accessing them will no longer crash your machine... neutral).

Anyway, I don't own a Mac, but does Apple not provide the necessary drivers through BootCamp?

Since there's only so much different HW in the Apple world, a DP would be rather small...

1,324

(8 replies, posted in Other)

Never heared of anyone using the DriverPacks with BartPE, but then again I never bothered with BartPE myself, either.

Don't see why it shouldn't work, though.
You basically install XP to a removable medium, such as a CD/DVD or a USB stick, right?
If space allows for it, you could also fit the DriverPacks on it.

Just make sure to enable KTD, so your OS will be able to detect as much hardware as possible.

www.memtest.org for Memtest 86+

http://ultimatebootcd.com/ very useful for all kinds of hardware checks, also includes Memtest 86+, so you only have to get this, really.