1,176

(14 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:

2) The WDM driver is missing in Catalyst 6.9 (the WDM_SP directory in the driver, that is), I'll keep on using the one from Catalyst 6.6, since that's the latest version in which it was included (although it's the same driver as the on in Catalyst 6.5, it has not been updated since 2004!). The WDM driver in the directory AVS_T200 is however still included in Catalyst 6.9, so I will keep on updating that driver.

Either I'm totally off and missed the huge thing that explains it all or there is indeed a version difference, as I posted...

DriverVer=04/04/2006, 6.14.10.1064
VS
DriverVer=07/06/2006, 6.14.10.1073

Or what is that file in the WDM dir for?

I'll guess I'll have to sleep over this first big_smile

Anyway, just checked and the WDM dir is indeed missing from the *FULL* file yikes

How could that happen?
Good thing I didn't update yet (no new MMC, no updating, my simple rules wink)

Or did they simply move the files to the main dir?
Because I do recognize a few files from there (AVS_T200.ini, atirt2xp.inf, ...)
Version included is DriverVer=08/01/2006, 6.14.10.1074, btw, just for comparison's sake.
So it's newer than that of 6.8.

Conclusion: one WDM driver was missing, NONE were outdated.

Hm, I'd really like to believe you but I'm not convinced, yet ;P

Guess I will have to try it for myself... wink

1,177

(6 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:
Helmi wrote:
Bâshrat the Sneaky wrote:

Already downloaded smile

Don't forget to include the WDMs this time! wink smile

I only forgot the WDM driver in the old Catalyst 6.5 driver in DriverPack Graphics B! wink And no, I won't forget it again.

But if you see this thread (http://forum.driverpacks.net/viewtopic.php?id=651), how do you explain the missing and outdated files in DriverPack Graphics A I encountered?

I did not however try whether they install correctly since I don't have the proper card in my test machine...

1,178

(6 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:

Already downloaded smile

Don't forget to include the WDMs this time! wink smile

1,179

(14 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:

I swore that page existed, but I just could not find it somehow! Thanks, Helmi!

NP smile

Yeah, personally, I found the old DL pages (as they were until some three years ago?) much more convenient.
Sure, this interactive script certainly does have its advantages here and there but I still prefer a simple ati.com/downloads/[currentdriverver] kind of structure for just DL'ing the drivers.

For tech support, Knowledge Bases etc this one may be superior but also much more confusing for the average user IMO.

1,180

(14 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:

I cannot find it on the internet, most sites refer to the ATI.com download, which is no longer operational.

That is strange, it still worked for me yesterday...
*puzzled*

6.5 *complete* driver:
http://support.ati.com/ics/support/defa … onID=22264

6.8 *complete* driver:
https://support.ati.com/ics/support/KBA … tionID=640

Just make sure not to follow direct links as they have an anti-hotlinking script in place.

1,181

(10 replies, posted in DriverPack Graphics)

Major wrote:

If you see in the image, there are 2 devices, one is Brother MFC-... (i know that is not included in the driverpacks), and the other is an USb device to which i refered.
Are the same?

Can't speak for borther but I know for my hp printer, there's two devices, too.

One is the actual printer and the other is the USB host driver for printers, which sort of emulates a parallel port, I guess (much like it emulates a serial port for my mobile if connected via USB, I guess).

Both of them should be covered by the brother printer, so try to get that printer installed first, then come back for any missing devices smile

1,182

(4 replies, posted in Installation Platforms)

twig123 wrote:

Best part of all, you can use it with Bâshrat the Sneaky's DriverPacks!!!!!!! smile

Very nice!
Never knew of this, thanks! smile

1,183

(6 replies, posted in DriverPack WLAN)

Ok, then apparently Bâshrat the Sneaky forgot to update the files somehow smile

You can easily find out which folder to look into by going to this page:
http://www.driverpacks.net/DriverPacks/ … k_WLAN.htm

Apparently, there's no driver version given ATM for the devices in question...


Bâsh, please fix smile

I'm about to reinstallmy notebook and also rely on this driver wink


In the meantime, I think you can just exchange the files with the newer ones, then repack the WLAN DP.

1,184

(6 replies, posted in DriverPack WLAN)

Huh?

The current (at least last time I checked...) version is 10.1.5.59, which correlates with the version included in the DP.

Or did you end up getting 10.1.1.3 installed somehow?

1,185

(6 replies, posted in Other)

Larce wrote:

thx again

ok i think  i success put all driver pack on to my windows xp folder and now try to covert to iso but i duno what i need to put on volume label..so do i need to put any thing on volume label?

Anything you want, really.
It doesn't matter, however, I would not use any non-alphabet symbols or leave it blank for compatibility.

EDIT:ok it work i format my computer and reinstall and it will detect all driver but space use about 3.5gb..

The price you'll have to pay...
Or you could do without KTD, that will use over 1GB less space.

so can i delete driver pack on my c drive?

If they are still on your HDD, youcan of course delete them once you slipstreamed them into a CD.
Other than that, using KTD, drivers will get stored to %systemroot%\driverpacks.
You could, of course delete them from there, however IDK whether that could cause an error should new hardware get found some day...

few question how to  add some app to my windows xp cd?like messenger anti virus,microsoft office etc..

That's the wrong forum for this kind of stuff, may I hand you over to http://unattended.msfn.org/unattended.xp/ as they deal exactly with this kind of stuff?

1,186

(14 replies, posted in DriverPack Graphics)

Sereby wrote:

and i use the driverpacks not with the "driverpacks base"..
i extract them and use my selfmade tool and with my selfmade setup.exe to search for the correct drivers in the dir with all the extracted driverpacks folders and it adds the correct paths into the registry ^^

Oh, I see.
That way, if there's an exception to be applied, it won't obviously, as that's all been ahndled by the BASE.

works perfect but there are no wdm files for my card.
i have to add them into the dir by hand

Did you already try the \D\G\A\1\WDM\ path out of DP_Graphics_A_wnt5_x86-32_609.7z?
That's where the WDMs are stored.

If those DO NOT work, they probably are incompatible with the pre-9600 cards which means Bâshrat the Sneaky has to add those older WDMs for complete compatibility.

ps: thx ^^ good to know

Yeah, keep up the great work! smile



EDIT:

Just compared the .INF files...

The one currently included in Graphics A:

; ATINTWDM.inf
; Win98/Win2000 Drivers for ATI AIW, AIWPro, TV Wonder, and ViVo video capture and playback devices
; Copyright 2002, ATI Technologies Inc.

[Version]
CatalogFile=atixpwdm.cat
signature="$CHICAGO$"
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=%atitech%
DriverVer=08/03/2004, 6.14.10.6246

The one from the 6.5 WDM pack:

; ATINTWDM.inf
; Win98/Win2000 Drivers for ATI AIW, AIWPro, TV Wonder, and ViVo video capture and playback devices
; Copyright 2002, ATI Technologies Inc.

[Version]
CatalogFile=atixpwdm.cat
signature="$CHICAGO$"
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=%atitech%
DriverVer=08/03/2004, 6.14.10.6246

So far identical, however, the 6.5 also contain another .INF, atirt2xp.inf

; Copyright 2005, ATI Technologies 

[Version]
CatalogFile=atirt2xp.cat
signature="$CHICAGO$" ;all windows os
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=%ATI%
DriverVer=04/04/2006, 6.14.10.1064

as well as several other files not present in the DP G A pack...



The 6.8 WDM pack contains the following info in the atirt2xp.INF:

; Copyright 2005, ATI Technologies 

[Version]
CatalogFile=atirt2xp.cat
signature="$CHICAGO$" ;all windows os
Class=MEDIA
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
Provider=%ATI%
DriverVer=07/06/2006, 6.14.10.1073

That all leads me to the conclusion that the WDMs included in DP G A are both outdated as well as incomplete.
They definately require some action from you, Bâshrat the Sneaky!

1,187

(6 replies, posted in Other)

Larce wrote:

i mean like can i download all driverpack then just let windows search my driver automatically?

Basically, that's how it works.
You use this tool (the BASE) to integrate ("slipstream") the drivers into your XPCD (which has to be copied to your HDD first, as you cannot write on the CD wink) and when that is done, Windows will treat those drivers the same way as those already supplied on your disc.
So, you only update them, so to speak.

It works all automatically and unless there's a bug, it will install all those drivers without further ado during XP installation, no user input required!

1,188

(14 replies, posted in DriverPack Graphics)

Oh, are they not included?

It's been a while since I installed on the machine equipped with my AIW 8500DV, but I do remember it did install the WDMs back then.

I would think they are in simply because they are part of the CATALYST pack...



Alright, I just checked and the Graphics pack A does contain the WDM folder, so logic would dictate (unless Bâshrat the Sneaky srewed it up completely wink) the same can be said about the actual driver files.

Since your card is a pre-9600 one, it is not supported by the latest CAT drivers (only <=6.5 will work).
This shouldn't be a problem for the WDMs, though, however, Bâshrat the Sneaky moved (or planned to do so) the pre-9600 drivers to Graphics Pack B, which, however, does NOT contain the WDM folder (not that it had to, as A already does so it could be taken from there, same as with the CP/CCC).

Now, what I'm guessing is there's either an exception missing to properly apply the WDMs on pre-9600 cards OR you didn't include Graphics Pack A.

Note to Bâshrat the Sneaky: WDMs are not only needed for AIW cards but VIVO ones as well, so there's quite a lot of users who'd rely on them.

Anyway, please give us more info about the included packs and post your finisher.LOG (which will also include the needed HWIDs).




PS: Congrats on your latest Update Pack, Sereby!
Working absolutely fine for me so far big_smile

1,189

(6 replies, posted in Other)

Check this thread (http://forum.driverpacks.net/viewtopic.php?id=578), please.

1,190

(2 replies, posted in Other)

I don't own a Mac, but at least I can tell you that the new models using Intel CPUs can run XP or Vista rather fine using Apple's BootCamp, so if you were to continue to use Windows, the Mac won't keep you from it wink

twig123 wrote:

A network share (from what I've been told) is the best way for client's systems to be installed... however, I haven't researched it much and would also like some incite if anyone would be so kind. smile

Yeah, I haven't dealt with thise too much, either, but would be interested to learn about it smile

All I know is that it requires the PC to be able to boot from the NIC (which will disqualify some systems) and you'll have to setup a special installation server from where it will get the boot image.

But what and how to do is completely beyond me ATM.
Then again, I haven't had the time to get any deeper into this anyway, so if someone could do a quick and dirty tut on this (just the basics, as I'm not computer illiterate otherwise wink, that would be fabulous!

Solid Archive does not have anything to do whether you create an ordinary of SFX archive.

Unless you want to extract specific files out of an archive or later add or remove files, Solid Archive is recommended since it will allow for greater compression.

Ususally, you should max all options, with respect to your maximum RAM size regarding Dictionary Size (RAM loadout will increase greatly once you push this so be careful not to exceed your physical RAM!).

1,193

(2 replies, posted in Other)

Hehe, maybe he added some of them this time.
Dunno whether he either forgot or was just busy since it took him quite a while to release this new version.

Anyhow, I'm aware of the problems with the Mobility driver, hence people in immediate need could use this tool to get it (hopefully) to work in the meantime.

Also, it was very clear to me you didn't apply them each time, that sounds like a waste wink
Obviously, only a new driver version would require reapplying and even then you could re-use the old INF file if nothing serious changed.

Was mearely meant as a heads-up, not trying to force you to anything big_smile

1,194

(2 replies, posted in Other)

Fort anyone who cares as well as for Bâshrat the Sneaky (because I know he's using it to create the Mobility-compatible drivers wink), after quite a long time, a new version of the ATi Mobility Modder has been released.

In a glimpse, it allows you to use the default ATi CATALYST drivers on virtually any notebook (eg for the Mobility Radeon cards).
This is a pretty good think because ATi's own Mobility driver only works on a handful of NB models and NB manufaturers ususally only have a year old drivers for DL sad

Get the good right here:
http://www.driverheaven.net/modtool/

Discussion is going on here (http://www.driverheaven.net/showthread.php?t=118092), so in case you card is not supported yet (most are, but you never know...), make sure you drop by!

Check this thread (http://forum.driverpacks.net/viewtopic.php?id=578), you should find all your answers there.

And, no, putting the drivers to "OEM\$1\drivers"  is NOT right!

FWIW, I found a changelog:

A3.92
Fix CD-In default volume issue
Support AMD CS5536(0x2093) chipset.
For special customize settings.
Uninstall issue when IS6.x built application in system .
A3.91
For special customize settings.
Update Realtek 3D engine.
A3.90
For special customize settings.
A3.89
Fix Fujitsu blue screen issue on BSOD on LANCE2.
For special customize settings.
Fix ATI chipsets can't enter C3 state issue.
A3.88
For special customize settings
Update Realtek 3D engine.
Fix delay issue in starting Windows.
A3.87 
Update Realtek 3D engine.
For special customize settings.
A3.86 
For special customize settings.
A3.85 
Update Realtek 3D engine.
For special customize settings.
For Fujitsu power management issue.
Write installation progress and result to "C:\ALCSetup.log" within silent mode .
Assign log file name and path for silent mode program issue .
Upgrade setup program to IS11.5 .
A3.84 
For special customize settings.
A3.83 
Support Sensaura filter driver.
For AC3 SPDIF issue when modem is present in ATI chipsets.
For special customize settings.
A3.82 
Fix 8-channel line-out noise issue in NVIDIA chipsets.
Update Realtek 3D engine.
For special customize settings.
A3.81 
Fix 8-channel noise issue for NVIDIA chipsets.
Fix "World Of Warcraft" game noise issue in ATI chipsets.
Update Realtek 3D engine.
For special customize settings.
A3.80 
For special customize settings.
For modem remote wake up issue in ALI chipsets.
A3.79 
Manual setup driver setting "Add and remove program" .
For special customize settings.

Also,
*bump*

smile

Now obsolete, see new post:
http://forum.driverpacks.net/viewtopic. … 4141#p4141

Link: http://www.realtek.com.tw/downloads/dlh … o%20CODECs

DL:

ftp://202.65.194.18/pc/hda/alc880d/WDM_R146.zip
ftp://61.56.86.122/pc/hda/alc880d/WDM_R146.zip
ftp://152.104.238.194/pc/hda/alc880d/WDM_R146.zip

Changelog:

1.46
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.

1.45
RtkHDAud.sys Version: 5.10.0.5286
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.

1.44  
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.

1.43
RtkHDAud.sys Version: 5.10.0.5283
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.


1.42
RtkHDAud.sys Version: 5.10.0.5282
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
2.) Fix some game issue .
CPL :
1.) Customization.

1.41
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.

1.40
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD, ALC660, ALC260,
ALC262, ALC268
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
InstallShield package :
1.) Correct present driver version in "Add or Remove Programs \ Support Information" .
2.) Windows 2000 installation reboot twice problem .

1.39
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC861VD,ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
2.) Add support for left panel and right panel config.
InstallShield package :
1.) Copy file rule in Vista system .
2.) Show driver version in "Add or Remove Programs \ Support Information" .

1.38
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
InstallShield package :
1.) Add "XP2K" and "Vista" folder name for installation .
2.) Abort flag setting .

1.37
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
? 3 ?
README.TXT
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
InstallShield package :
1.) Upgrade to IS11.5 .

1.36
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC888, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
2.) Add ALC888 .
CPL :
1.) Customization.

1.35
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.

1.34
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
2.) Fixed Adobe Premiere Pro 1.5 Crash issue .
CPL :
1.) Customization.
InstallShield package :
1.) Rtlupd termination return error code .
2.) Receive error code rule from Rtlupd SetupAPI .
3.) SetupCopyOEM install rule .

1.33
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
InstallShield package :
1.) Bus driver detect issue .

1.32
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
CPL :
1.) Customization.
InstallShield package :
1.) Report installation progress and result to "C:\RTHSetup.log" within silent mode .
2.) Rtlupd setup API will not appear message dialog in silent mode .

1.31
1. Codec Supporting: ALC880, ALC882, ALC883, ALC885, ALC861, ALC260, ALC262
2. OS Supporting: Microsoft WindowsXP, Widnows2000, Winx64
3. Pack with Microsoft High Definition Audio UAAV1.0a(5013)
4. Add/Fix
1.) Customization.
For New architecture:
1.) Customization .
2.) Add ALC885 HD Audio Codec for WHQL .
CPL :
1.) Customization.

1,199

(5 replies, posted in DriverPack Graphics)

Bâshrat the Sneaky wrote:

6. Now delete ALL files in "C:\ATICCC_dps" except for ISScript9.Msi.
7. Move everything inside "C:\ATICCC_Spanish" into "C:\ATICCC_dps".

Couldn't you just overwrite existing files for the same effect?
I would think that filenames are the same regardless of the language used.

twig123 wrote:

Aren't Matrox cards supposed to be installed ONLY after the windows install is complete?
Otherwise it will pick up the firewire on the card as a standard firewire jack (which it is not). true?
Or is the version of cards without the extra firewire?

Not directly related and just FYI:

I certainly haven't had an issue with my old AIW R8500 DV, which also featured two FW ports (which was quite an innovation back in the day when most PC users hadn't heared of FW before).

Thankfully, they appear to be standard jacks (6 pins) and you can also selectively disable them on the board with DIP switches.