mickmack wrote:

ok. i have G-Skill DDR500 which is working at 520 and i never had a pboblem. last night i spend on changing slots, changing memory, underclocking memory, and testing, testing, testing. so my conclusion after all is that if WINNT.SIF with all integrated drivers is in I386 folder, setup fails, if i remove PNPDRV lines, setup is ok. i don't have a clue what could it be? and why.

Well, if it DOES work when you use method 2, then you'd have convinced me half the way... so just try method 2 as DriverPacks Method and then let uw know if it worked.

P.S.: you speak Russian and you live in Antwerp??? tongue

mickmack wrote:

the problem is in WINNT.SIF. maybe it has something to do with WINNT.SIF limitations. i integrated all the packs including 3rd party, and got blue screen. then i removed PNPDrivers paths in WINNT.SIF and no blue screen.

That's not a valid conclusion. You assume that the cause lies in the very method that is used that allows setup to install drivers. Or more specific: you think it's caused by the way the DriverPack Sound B has applied that method.

Drivers are still being loaded correctly: else you'd have gotten an error about an invalid line in the winnt.sif file. It really is a driver conflict, or a driver that is failing (although that is very unlikely).

EDIT: after searching for '0x8e bsod setupdd.sys' it seems that the best hits even refer to the old DriverPacks forum at MSFN.org tongue One was due to a corrupted CD/ISO, one was due to 'an error in my process of creating the multibootDisc' and the last one was due to faulty RAM.

According to KB315335, it has GOT to be your RAM. So please put some other RAM sticks in it, even if only temporary. This is the resolution, according to Microsoft:

RESOLUTION
To troubleshoot this behavior, follow these steps:
1.    Remove some of the memory modules that are installed on the computer. Leave at least the RAM that is required for the computer to start and run Windows XP.

The recommended RAM to run Windows XP is 128 megabytes (MB). The minimum is 64 MB, and the maximum is 4 gigabytes.

For example, if two 256-MB memory modules are installed on your computer, remove one of the memory modules.
2.    Restart your computer, and then run the Setup program:
a.    Insert the Windows XP Setup CD-ROM in the CD-ROM drive, start the computer, and then click OK to select the first option screen to install a copy of Windows XP.
b.    Click Accept, and then follow the instructions on the screen to complete the Windows XP installation.
3.    If you again receive the error message that is mentioned in the "Symptoms" section, go to step 4.
4.    Remove a different memory module, or install the RAM in a different memory slot.
5.    Restart your computer, and then rerun Setup.

You may have to restart your computer several times to identify the specific memory modules that are not working correctly.

I'm sorry, but there isn't much I can do about this!

1. Releases

When you post a new topic for a new or updated 3rd Party DriverPack, do it according to this rule:

TOPIC TITLE
"[REL] DriverPack xyz y.mm" where 'xyz' is the name of your DriverPack, 'y' is the current year (i.e. '6' for '2006') and 'mm' is the current month (i.e. '08' for August, '12' for December). Only post DriverPacks for the wnt5_x86-32 platform in this forum.

TOPIC CONTENT

DriverPack xyz y.mm

[u r l=http://3rdpartydriverpacks.thesneaky.com/wnt5_x86-32/DP_xyz_wnt5_x86-32_ymm.7z]Download[/u r l]
[u r l=http://3rdpartydriverpacks.thesneaky.com/wnt5_x86-32/DP_xyz.htm]Changelog[/u r l]
MD5 : <MD5 hash> (You can use HashTab to find it![/url])
Compressed size: n.nn MB
Decompressed size: o.oo MB
Rootdirectory: D\X (where 'X' is preferably the first letter of 'xyz', if already taken, the first AND the second, if already taken...)
Contributors: John Doe, Homer Simpson, Queen Elizabeth and George W. Bush (these are fictional names, please replace by your own wink)

(entries in italics are optional)

I see you do not yet have a bugtracker account. If you'd like to have one, you can submit the issue yourself, else I'll submit it.

See bug #90, already fixed in the next version.

I did not know you had that ability... will be disabled tomorrow, to prevent some serious problems in the future.

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

ricktendo64 wrote:

Problem is im not the French translator Maxximum is

My spanish one is Alt compatible

Doesn't matter to me, I just wanted to give an example... Didn't care in what language, I just used yours wink And if that's the case, maxximum will get complaints so he'll definetely change it wink

1,484

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

Sm0k3r wrote:

Bashrat i've just made an donation hope the nominal fee i've sent helps.  For confirmation my email is yoz7120@hotmail.com.

Wow! That's a very nice donation smile Thanks alot!

P.S.: I suppose you're using the DriverPacks for professional goals, then?

1,485

(12 replies, posted in DriverPack LAN)

Changelog
new
-D-Link DGE-528T
-IC Plus IP100
-Realtek Realtek RTL8111(B)/RTL8168(B)
-TrendNet TEG-PCITXM
-TrendNet TEG-PCITXR
-TrendNet TEG-PCIBUSR
-TrendNet TEG-PCITXM2

updated
-Intel 10 Mb, 100 Mb, 1 Gb, 10 Gb drivers from 01/12/2005,8.0.27.0 & 01/23/2006,9.3.28.0 & 01/04/2006,2.1.11.0 [10.3] to 01/12/2006,8.0.27.0 & 06/05/2006,9.4.17.0 & 01/04/2006,2.1.11.0 [11.0]
-Marvell Yukon driver from 04/06/2006, 8.53.1.3 to 07/06/2006, 8.56.4.3
-nVidia nForce Ethernet drivers (only updated those for nForce 4 and 5)
-Realtek 8139(A/B/C/D/8130)/810X/8169/8169S(B)/8110S(B) driver from 05/19/2006,5.641.0209.2006 [6.41] to 07/19/2006,5.649.0615.2006 [6.49]
-Realtek 8150 driver from 03/19/2004,5.1191.0319.2004 [1.21] to 04/28/2006,5.122.0510.2006 [1.22]
-SiS 900 driver from 12/19/2005,2.0.1039.1181 to 02/22/2006,2.0.1039.1190 [1.19]


Known issues
-nVidia nForce 3 ethernet: a workaround has been implemented, confirmation is still needed that it's working though

Remarks
-If you have an nForce 3-based motherboard please report BOTH if it is working or NOT working

Download

Latest ForceWare drivers cause system crashes
by Cyril Kowaliski - 12:48 am, July 12, 2006

NVIDIA's latest official ForceWare graphics drivers cause serious system crashes when combined with motherboards based on the new nForce 570 SLI chipset, according to a report at HardOCP. The 'OCP tested two nForce 570 SLI mobos in systems outfitted with the latest nForce 570 SLI/570/550 9.16 platform drivers and ForceWare 91.31 graphics drivers, and in both cases the machines apparently suffered from not only crashes, but also data corruption. According to a Taiwanese source quoted by the site, problems with the new ForceWare drivers also occur in systems with Intel 955X chipsets.
Neither HardOCP nor its Taiwanese source give specifics on the frequency of these problems, but both suggest NVIDIA's ForceWare 91.33 beta drivers—available from the nZone website—fix the problem.

Amusingly, this report comes on the same day as NVIDIA's boastful press release about achieving "excellent" stability results in a Veritest study. NVIDIA says Veritest found that PCs built around the NVIDIA Business Platform passed a high-stress 15-day burn-in test, while one of the competing Intel-based systems failed the same test after 24 hours. Veritest concluded that NVIDIA Business Platform systems were "as stable, if not more stable" than the competition.

source

1,487

(1 replies, posted in DriverPack WLAN)

These are WLAN drivers, not LAN wink Moved to DriverPack WLAN forum.

http://support.microsoft.com/?kbid=901105

Yes, then you should use the next letter, in your example that would be 'Sortir'.

I meant DriverPack Sound B 6.08 wink

It's fixed in 6.08: no one has reported this bug again!

1,492

(10 replies, posted in Translations Team)

Thanks!

Could you please tell me the exact translation for 'Russian' in Russian? It's for the new .lng filename naming scheme (check the sticky).

shaz wrote:

The hotfix doesn't fix only the midi software but also other hotfixes.
This is a cumulative hotfix. All previous hotfixes concerning portcls.sys are also supported by this hotfix.

So it is wrong to say that 0.01% of the people are helped by this hotfix.

I am using this hotfix. No problem so far.

Of course it's cumulative... that's always.

I'll implement as soon as RyanVM confirms it's good to go. He's the Updates Master, so his word will make or break it.

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

Not everything went well wink I want it to be bugfree. Only one bug to go...

1,496

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

McStarfighter wrote:

Bashrat, it is more important for me to support the project than to get any kind of title. When it is possible, then OK.

Well, I did owe you an explanation, so that's what you've got wink

1,497

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

coreytk wrote:

Hi Bâshrat,
I am a blind computer user and I have found your driver packs very useful I have also donated $10 Euros you should see the email corey@hvc.rr.com thanks again for the terrific job I really appreciate it.

Thank you very much! smile

I've made you a member of the Donators user group. In the future, you will automatically be added to this user group by the way.

1,498

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

McStarfighter wrote:

Now I've donated my 10 Euro, too. It comes from mcstarfighter@gmail.com.

You're already a beta tester, cannot make you a donator too... That's one of the lacking features of the forum software I use, but I will install a mod that makes it possible somewhere in the next few weeks. I chose this forum software for its speed, by the way wink

Known bug: bug #72. It's fixed in the next version.

KB888111 is language independent. wink