EH?

I tested this... can somebody else confirm?

Only if you don't use the old DriverPacks anymore: YES. (For whatever reason you might not want to update.)

1,853

(12 replies, posted in DriverPack LAN)

razormoon wrote:

hmm..it's probably me. But I keep getting page not found after terms of use (Download Driverpack!). sad

Fixed.

EDIT:

I see now that I didn't update the Realtek driver sad. Update tomorrow.

1,854

(8 replies, posted in Other)

They're out wink

The website isn't completely up-to-date though. That's for tomorrow... no more time!

1,855

(0 replies, posted in DriverPack WLAN)

Changelog
-new: support for ALL Accton WLAN controllers.
-new: support for U.S. Robotics USR(80)5417 WLAN controller.
-updated: AVM FRITZ! WLAN USB Stick driver from 10/18/2005,01.02.17 to 04/06/2006,2.0.4.1482.
-updated: D-Link DWL-G122 driver from 03/11/2004, 1.00.13.0 to 08/05/2004, 3.00.22.0.
-updated: Intel 2200BG; 2915ABG, 3945ABG driver from 09/12/2005,9.0.3.9 [9.0.3.9] to 04/04/2006,10.1.1.3 [10.1.1.3].
-pdated: Netgear WG511T driver from 08/13/2004,3.3.0.156 to 08/13/2004,3.3.0.156 (.inf updated).
-updated: Belkin F5D7001, F5D7011 driver from 02/19/2004, 3.50.21.11 to 02/18/2005, 3.100.64.0.

Known issues
-none

Remarks
-none

Download

1,856

(12 replies, posted in DriverPack LAN)

Changelog
new
-support for ALL Accton NIC's.

updated
-Broadcom 57xx, 58xx, 59xx driver from 10/31/2005,8.48.0.0 to 10/31/2005,8.48.0.0 [8.48e] (null update)
-Marvell Yukon driver from 01/04/2006, 8.49.2.3 to 04/06/2006, 8.53.1.3
-VIA Velocity VT6120, VT6122 driver from 06/14/2005, 1.44.0.102 [24] to 06/14/2005, 1.44.0.102 [25]

Known issues
-none

Remarks
-none

Download

1,857

(0 replies, posted in News)

Changelog
New (repeated from 6.05 CP)
-[GUI] new: GUI!
-[slipstreamer] new: full support for Windows 2000 and Windows Server 2003
-[slipstreamer] new: QuickStream Cache
-[slipstreamer] new: several new KTD options
-[slipstreamer] new: unattended slipstreaming
-... and much more

Fixes (bug ID's from bugtracker)
- 0000039: [slipstreamer] TXTSETUP.SIF: Invalid entries in [DiskSpaceRequirements] (BashratTheSneaky)
- 0000040: [GUI] When Finishing Method ="custom" in settings file, this setting isn't imported (BashratTheSneaky)
- 0000030: [slipstreamer] Critical Error! - No suitable slipstream module found (BashratTheSneaky)
- 0000036: [slipstreamer] MsDosInitiated line created in WINNT.SIF regardless of if it already exists. (BashratTheSneaky)
- 0000031: [slipstreamer] makePNF.exe shows during first boot (BashratTheSneaky)
- 0000038: [slipstreamer] DPs_fnsh.cmd: agrep -s -ci "*PNPB02F" %T% line produces error. (BashratTheSneaky)
- 0000033: [slipstreamer] M1+RunOnceEx:: Missing files, missing directories. (BashratTheSneaky)
- 0000032: [slipstreamer] KTD enabled: drivers directory deleted (BashratTheSneaky)
- 0000026: [GUI] M1+RunOnceEx: if no $OEM$ dir exists, then it won't be created and as a result RunOnceEx won't work (BashratTheSneaky)
- 0000029: [slipstreamer] M2+RunOnceEx: if no $OEM$ dir exists, then it won't be created and as a result RunOnceEx won't work (BashratTheSneaky)
- 0000028: [GUI] when RunOnceEx as Finishing Method, but no RunOnceEx Settings set: AutoIt Error (BashratTheSneaky)
- 0000022: [slipstreamer] multiboot, M2: DPs_fnsh.cmd not working properly (BashratTheSneaky)
- 0000024: [slipstreamer] invalid & incomplete DP MassStorage text mode entries in txtsetup.sif (BashratTheSneaky)
- [slipstreamer] API mode: immediate crash

Known issues
-[GUI] When doing the following sequence: UpdateChecker -> Overview -> UpdateChecker, there's a GUI bug
-[slipstreamer] DriverPack MassStorage text mode doesn't work properly when using Windows 2000 (NTLDR missing error)
-[slipstreamer] multiboot support is not yet operational

Remarks
-Documentation in DriverPacks BASE 6.05! Just use it as-is now. It's all pretty self-explanatory...
-You have to rename the DriverPacks! An example: "DriverPack_Graphics_A_V603.7z" must be renamed to "DP_Graphics_A_wnt5_x86-32_603.7z". If you download any DriverPack now, they will already have the correct names.
-You should slipstream the new DriverPacks in a fresh source!
-This version may still contain bugs, but it shouldn't be many!

Download

1,858

(26 replies, posted in Other)

Eh? How were they INcompatible in the past?

Floppy wrote:

Is this path a problem?  C:\Downloads\driver\DPs_BASE
Do I need Framework (dotnet11sp1.exe) ?

That path is ok. And nope you dont need the .NET framework.

muiz wrote:

i removed the "=" but that  did NOT the trick.

Now i get a BSOD

http://img523.imageshack.us/img523/3576 … 7uz.th.jpg

Eh? That file isn't even touched by the DriverPacks BASE. Probably you edited another line in the txtsetup.sif file without even knowing!

New version will be online within two hours at the most.

That's ok... then I don't know what the problem is... Very strange! Tested here with DP Chipset 6.05, M1 and Windows XP SP2 and it's working just fine, as for at least several others. In 6.05 the error message is fixed, so it shows which subdirectory of D\C\I it's trying to use. It'll be easier to find the cause then.

And you did NOT rename the old DriverPack Chipset to 6.05? Please check its filesize and report back.

This is not necessary for method 2 and therefore you don't get that error when you use method 2.

Do you ALSO have DriverPack Chipset 6.03 in the DriverPacks directory? If so, that's the cause. Please delete it.

You aren't using DriverPack Chipset 6.05, are you? You MUST update to the latest one.

Crap... PunBB doesn't support splitting topics yet... That sucks bigtime! Nor moving posts... even worse! Let's hope PunBB 1.3 will be released soon!

I'll change the topic title to reflect both bugs...

Both of you are using Windows XP SP2? Not that that should matter, just trying to narrow down the problem.

Eh... Nope :s

I checked immediately in my last test, and I don't have those entries? They should be listed in the sections [files.atiide] and [files.aliide], not there. Could you slipstream it again please?

dumpydooby wrote:

I was pretty sure this was already implemented into the GUI version.

Nope...

It's this setting in the winnt.sif file:

MsDosInitiated = 0

0/no : started through network or CD, required for unattended installations
1/yes : started through DOS, e.g. floppy, enables F6 option

I'll add this as an option to select in the GUI, default will of course be 0 (as it is now)

EDIT:

As a reference: KB216258.

1,869

(26 replies, posted in Other)

When PunBB 1.3 will be released, it'll be super easy to add functionality. Expect some very nice improvements then wink big_smile

This only happens if you haven't selected a location yet. Then it's quite normal to get that error: how could one slipstream the DriverPacks if no valid location is specified and therefore no OS detected? If no OS is detected, the slipstreamer isn't able to choose a certain slipstream module...

I can see by your post in the bugtracker that you were using DriverPack Chipset 6.03.1 instead of 6.05. Please DELETE the old DriverPack Chipset! It will be detected instead of the newer one.

EDIT: doh that wasn't you, that was 'mkp'... Sorry. Here's the [ur=http://bugtracker.driverpacks.net/view.php?id=37]link[/url] btw.

I never was able to reproduce your issue... sad

1,873

(26 replies, posted in Other)

That's why I didn't understand... I always use ctrl+left click or right click> open in new tab (Firefox)...

And I'm afraid that's not an option in PunBB... and I don't feel like modifying it. Perhaps it will become an option in one of PunBB's next versions.

1,874

(26 replies, posted in Other)

Camarade_Tux wrote:

Really nice.

Could we have this theme : http://www.punres.org/viewtopic.php?id=1524 ?
Sorry, couldn't resist. tongue

Oh and may the force be with you.
....argh ! I too have exams!



edit: could you please make links in messages open in new windows ?

Eh............ NAH! tongue

What do you mean by "links in messages open in new windows"?

twig123 wrote:

I also checked and there are more .ORG backup files in I386 folder....
anyways, if it is not a typo... then I can only assume that the reason for the .ORG files are short for 'original'
... I'm just use to the .old naming..... but its your software wink

Keep up the excellent work!

Very correct.

I just felt 'original' is better than 'old' and at the same time this prevents the DriverPacks BASE from using the old backup files. (You should slipstream the new DriverPacks in a fresh source.)