muiz wrote:

It works finaly , after a long time.
I dont use raid , so i cant confirm that.
it still meses up cmdlines.txt , but bashrat is going to fix that.

So we are 1 step closer to a final?

There will never be a final! wink

As the drivers and their respective issues evolve (updates and new drivers), the DriverPacks BASE will have continuously to be updated. A 'truly stable version' is the the definition I'd like to use wink

You should do it like this to be very sure:

[GuiRunOnce]
command1="%systemdrive%\install\net.exe"
command9="%SystemDrive%\fnsh_log.cmd"

And I was aware of the fact that the SETTING isn't saved, but did NOT know that neither of them got installed. Did you use method 1 or method 2? If you're using method 1, there should be a ATICCC.ins/ATICCP.ins file in your \$OEM$\$1 dir, when you're using method 2 either of those files should be in the \OEM dir. Please report back!

1,753

(1 replies, posted in Feature Requests)

Somewhere after my exams wink

Nope. The installation will fail then, it will give you an error message that says "CLI.exe is missing".

According to muiz's latest test it's "working like a charm with 6.06", so can others please confirm? Then I can get rid of this sticky immediately tongue

chertoianov wrote:
Bâshrat the Sneaky wrote:

You can do a filehash comparison if you don't trust me, but I guarantee you that cmdow.exe has NOT changed and that it does NOT contain malware of any kind.

Don't say that! You are one of the men who i trust most.
I just ask myself, why in the older version was no that problem.
I found the solution of my problem when i exclude path of driver pack base from scan.

The explanation is simple: the AV makers have updated their definitions. I guess that if you'd scan the old DriverPacks BASE (pre-6.05), that you'll get the same error message now wink

1,757

(6 replies, posted in Feature Requests)

This will become a built-in feature of the DriverPacks BASE! wink

Note that this will only trigger warnings, not prevent slipstreaming. If I'd prevent slipstreaming an 'unverified' DriverPack, then my users would be unable to modify the DriverPacks to their liking. It's only a few who do so, but I don't want to make things more difficult for them.

It seems the DriverPacks don't work very well in combination with MCE (according to razormoon and muiz)... So please post your experiences, tips and anger outbursts here (:D), so we can get it solved quickly.

Current status:
-not the slightest clue why at least the text mode drivers aren't working!

If it's still not working, just post a screenshot of your "3rd party DriverPacks" directory. I'm sure there's something wrong with the filenames.

You can do a filehash comparison if you don't trust me, but I guarantee you that cmdow.exe has NOT changed and that it does NOT contain malware of any kind.

1,761

(0 replies, posted in DriverPack Sound)

Changelog
new
-support for VIA HD Audio

updated
-Realtek AC'97 driver from 02/17/2006,5.10.00.6030 [3.84] to 03/17/2006,5.10.00.6050 [3.85]
-Realtek HD Audio driver from 03/08/2006, 5.10.0.5229 [1.33] to 05/04/2006, 5.10.0.5253 [1.37]
-VIA Envy driver from 01/12/2006,5.12.01.3650 [5.00a] to 01/12/2006,5.12.01.3650 [5.00b]
-VIA Vinyl driver from 11/25/2005,6.14.01.4150 [6.50a] to 04/13/2006,6.14.01.4160 [6.60b]


Known issues
-none

Remarks
-none

Download

1,762

(7 replies, posted in DriverPack Graphics)

-If you remove only a few components with nLite, it will already easily fit. (Did you already remove the upgrade directory already btw?)
-I know the 7800 Go GTX is supported by the other drivers as well, but the one in D\G\N\2 provides WHQL support.
-The 91.28 drivers do not support all Quadro models.

You know that you should only use the DriverPacks you really need, which implies that DriverPack Graphics C would be completely useless for most people.

But yes, ruudboek, as far as I can tell, this procedure should result in a working installation disc.

1,763

(7 replies, posted in DriverPack Graphics)

Changelog
new
-nVidia GeForce (Go) driver with complete 7 series support (temporarily added)

updated
-ATI Radeon driver from 02/21/2006, 8.231.0.0 [6.3] to 05/03/2006, 8.252.0.0 [6.5]
-ATI Mobility Radeon & Mobility FireGL driver from 02/21/2006, 8.231.0.0 [6.3] to 05/03/2006, 8.252.0.0 [6.5]
-nVidia GeForce (Go) driver from 12/10/2005, 8.1.9.8 [81.98] to 03/09/2006, 8.4.2.1 [84.21]

Known issues
-none

Remarks
-Not compatible with the old DriverPacks BASE (pre-6.06)!

Download

1,764

(0 replies, posted in News)

Changelog
New
-[slipstreamer] KB883667 support (Windows XP SP1 and SP2, non-MCE)
-[slipstreamer] M2: if some files present in $OEM$ dir, set OemPreinstall="yes"
-[slipstreamer] 3rd party finishing scripts (%SystemDrive%\3pscript.cmd will be executed just before the cleanup)

Fixed (bug ID's from bugtracker)
- 0000059: [GUI] KTD="select": settings properly saved but not properly imported (BashratTheSneaky)
- 0000058: [slipstreamer] .INI: DriverPacks="select" and in [SelectDriverPacks] all DriverPacks selected: not all DriverPacks slipstreamed (BashratTheSneaky)
- 0000054: [GUI] When older version of an official DriverPack is also available, the newer version isn't detected (BashratTheSneaky)
- 0000057: [slipstreamer] M1: \$OEM$\$1\cmdow.exe missing (BashratTheSneaky)
- 0000055: [slipstreamer] KtD for Method 2 not actually Keeping the Drivers! (BashratTheSneaky)
- 0000053: [GUI] autoupdating the DriverPacks BASE not working properly (BashratTheSneaky)

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 later this week! 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 should be VERY FEW!

Download

1,765

(44 replies, posted in Other)

clubcj, it seems you were also on the blacklist. Same advice as I gave to mgadallah: don't use any crappy download manager, they create an enormous, unnecessary load on the server.

Problem 3 is solved in the next DriverPacks BASE!

Yes you can download it with anything. But please don't use crappy download managers, they create an unnecessary high load! wink

1,768

(8 replies, posted in Other)

Sanjay wrote:
Bâshrat the Sneaky wrote:

Today at the very least updates of DriverPack LAN and WLAN (and Chipset will be made 'official', i.e. the site will be updated), probably also Graphics A and Sound A.

Was just wondering whatever happened to the 'Graphics A' & 'Sound A' updates. Also, when can we expect an update for 'Mass Storage'?

Thanks.

They will all get an update! wink

Sorry for the slow resolution of this issue. It seemed you were on my blacklist after all. That means you must have been using a VERY bad download manager, since I only blocked  IP's with >500 requests/day. Which is quite excessive, don't you think? I'll check my blacklist faster from now on.

Sorry for the problems!

No... then just disable the device - it won't affect your system negatively. You cannot expect all devices to be installed if you don't slipstream all drivers... wink

Do a search for "cli.exe"!

wink

Well, that line is not necessary when using method 2. But I'll add detection of files inside the $OEM$ dir: if any files are detected, the line will be added nevertheless! wink

1,773

(44 replies, posted in Other)

It's working for everyone else :s

hehe tongue

That's the easiest part by far wink

1,775

(8 replies, posted in DriverPack Sound)

yikes

Damn I did not know that, thanks! Quite strange though... I guess the software would alert you? But then it'd have to be the control panel, since no other software would be installed when using the DriverPacks.