ruudboek

That doesn't matter if it works. Are you gettings any errors, BSOD's, or is there no sound comming out? Ruud

Yes, i boot from CD into DOS. I created a menu in which i can select different partitioning options. After partitioning i can choose to specify a computername and after that winnt.exe is started. I am using the i386 folder on the CD itself. Regarding the compatibility of the driverpacks with the 8.3 format i can tell you that the next autoit version of the driverpacks is going to be fully 8.3 compatible. I know this because i have joined the betatesting of the new autoit version of the driverpack base. So far it works great. Ruud

@theUtmost First of all i don't use dos to start the installation from the network, i also start it from CD. However, if i remember correctly, when you start the installation from DOS, the default location of the $OEM$ will be INSIDE the i386 folder. The BTS driverpacks require that the $OEM$ folder is in the root of the CD, therefore i had to add the following line in the [unattended] section : OemFilesPath = "\$OEM$" That did the trick for me. Ruud

@filu could you please post your hardware id's? Maybe this problem is due to the presence of 2 drivers with the same hardware id's. Ruud

Hello all, F.Y.I i made a comparison of all the Realtek AC '97 drivers and the rest of the drivers in the driverpacks Sound A (603) and B (603). I found out that 821 hardwareid's are present both in the Realtek AC'97 drivers aswell as in the remaining drivers of the driverpacks Sound A and B. So those are duplicate hardwareid's. Please find attached a text file in which all these duplicate hardwareid's are listed. Ruud Duplicate_hardware_id__s_Realtek_AC97_vs_Rest_of_Driverpacks_sound.txt

Count me in Ruud

@mediapla it's great to hear you confirm my findings . I think there are probably many more hardware-id's that can be remarked or removed from those realtek ac'97 inf files. But still, the question remains, what are those non-realtek hardware-id's doing there? Ruud

Ok i have so far written and send the following letter to pctech@realtek.com.tw: Dear miss, sir, i found out that the PRESENCE of your AC'97 driver in an unattended installation of Windows XP is causing blue screens of death when installing the unattended installation on a ASUS K8S-MX mothboard. I found out that your driver instead of the Asus Soundmax sounddriver is being used during the installation. Apparently YOUR driver is detected and installed by Windows XP instead of the Soundmax driver from ASUS. After the first reboot of the unattended installation, Windows XP loads YOUR driver and that causes the blue screen of death. Now when i completely remove your driver from the unattended installation, no problems seem to occur. When i look closer at the inf files of your driver, i found out, to my suprise, that the hardware-id of the Asus Soundmax soundcard was actually present in one of your inf files. I now have the following questions: 1. What on earth is the hardware-id from one of your competitors doing in one of your inf files? 2. This above mentioned problem has been reported also with lots of other Soundmax compatible soundcards from lots of other manufacturers. The same blue screen of death occurs with those soundcards aswell. When i remove your AC'97 drivers no blue screens of death seem to occur anymore. Why does your driver cause the BSOD's for so many other Soundmax hardware aswell? 3. What can i do, or what are you going to do to solve this problem? For more information: The error mention on the blue screen of death is the following 0x7E, portcls.sys The ASUS soundmax hardware-id is the following : VEN_1039&DEV_7012&SUBSYS_810D1043&REV_A0\3&267A616A&0&17 The ASUS K8S-MX soundmax driver can be found here http://support.asus.com/download/download....SLanguage=en-us You can find more informating regarding the reported probems in the forum of this driverpack project: http://www.msfn.org/board/index.php?showtopic=60550 But also here : http://www.msfn.org/board/index.php?showto...rtcls\.sys Bear in mind that your answer will be posted in the same forum.

Has anybody taken the trouble to actually report these serious BSOD bugs at Realtek? Maybe we should work on a letter in which we make clear that the presence of their drivers cause BSOD's with OTHER manufacturers hardware. I think those other manufacturers might also be very interesting in this information. Maybe we can also push the people at realtek to solve this bug ASAP by checking if their driver's behaviour is a direct violation of the Microsoft driver signing policy (WHQL). What should we put in that letter? Ruud

New Realtek AC'97 drivers version 3.85 are out. Can someone with an ASUS K8S-MX motherboard try to follow this procedure to see if the portcls.sys error is gone? Hereby the steps to take : 1. Download the latest Realtek AC '97 drivers from : http://www.realtek.com.tw/downloads/dlac97...8&Software=True ( Size should be 17720k) 2. Extract the downloaded WDM_A380.exe with 7zip. 3. Extract the driverpack sound A with 7zip. 4. Delete the Contents of D\S\R folder, except for the D\S\R\HD folder. 5. Go back to the folder in which you extracted the WDM_A385.exe file and copy the CONTENTS of the WDM folder to the D\S\R folder. 6. 7Zip the D folder with maximum compression (archivename has to be the same as the name of the driverpack sound A). 7. Do a new slipstream of the driverpacks. 8. Done! Ruud

http://www.realtek.com.tw/downloads/dlac97...8&Software=True Changelog : A3.85 - 1. Update Realtek 3D engine. 2. For special customize settings. 3. For Fujitsu power management issue. 4. Write installation progress and result to "C:\ALCSetup.log" within silent mode . 5. Assign log file name and path for silent mode program issue . 6. Upgrade setup program to IS11.5 .

I am also starting the installation from DOS and i have a few extemely good reasons why starting the installation from DOS is superior to starting it directly from the bootable part of Windows XP or WinPE. 1. I want to be able to partition the whole harddrive before the installation starts. I created a dos menu by which you can choose to what size partition C and partition D should be created. So for example C 10% and D 90% or C 20% and D 80% or C 30% and D 70%, etc. When they make a choise gdisk.exe creates the partitions accordingly. Now ofcourse you will say, you can do this by using WinPE instead of DOS aswell. But, Winpe is A ) way to slow to start and B ) consumes way to much badly needed space on the unattended CD. 2. I use DOS to enter the computername before the installation starts. Now ofcourse you will say that if you will leave out the computername from the .sif file the unattended installation will prompt you. True, but it takes way to long before you get prompted. Bottom line : With DOS i can partition and enter the computername in seconds, i don't have to come back after 10 minutes to check to see if the computername prompt is there already AND it saves me a LOT of valuable CD space because i don't use WinPE. Therefore please do not forget about the fact that there are people still using DOS to kick off the unattended installation unless ofcourse someone can persuade me otherwise. I would really appreciate it if these files would get renamed so that they are compatible with the 8.3 convention. To my opinion it is only logical to do this, since the original Window XP CD is 8.3 compatible by default and so is probably every uncompressed driver, why deviate from an globally accepted standard that even crappy realtek accepts ?

@5eraph, there is no quarantee that those unified drivers will solve all the nforce problems i think, so if we can solve those nforce problems right now, i'd prefer that. I think the solution proposed by RyderOCZ sounds excellent. Have any problems with the Intel nforce chipset been reported in the past? If not, why not keeping those 4I and 4IR folders the way they are and implement the solution only in the 4A and 4AR folders? @Bashrat, what do you think of this? Ruud

@5eraph Can you confirm that this solution works for you too? Ruud

@Bashrat, how are you going to detect the correct nforce drivers to delete during textmode setup? Ruud

@Bashrat Sorry for the late response, i was only recently able to get a hold of the owner of one of the 2 same computers involved. These are the hardware id's of the computer on which i have not yet installed the latest VIA Vinyl 6.50a drivers, so no sound comming out of the speakers: =========== PCI devices =========== PCI\VEN_10DE&DEV_0181&SUBSYS_80631043&REV_A2\4&618BA55&0&0008: NVIDIA GeForce4 MX 440 with AGP8X PCI\VEN_10DE&DEV_0322&SUBSYS_00011B13&REV_A1\3&61AAA01&0&48 : NVIDIA GeForce FX 5200 PCI\VEN_1106&DEV_0571&SUBSYS_05711106&REV_06\3&61AAA01&0&89 : VIA Bus Master IDE Controller PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&80 : VIA Rev 5 or later USB Universal Host Controller PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&81 : VIA Rev 5 or later USB Universal Host Controller PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&82 : VIA Rev 5 or later USB Universal Host Controller PCI\VEN_1106&DEV_3059&SUBSYS_18411019&REV_50\3&61AAA01&0&8D : Realtek AC'97 Audio for VIA ® Audio Controller PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_74\3&61AAA01&0&90 : VIA Rhine II Fast Ethernet Adapter PCI\VEN_1106&DEV_3099&SUBSYS_00000000&REV_00\3&61AAA01&0&00 : VIA CPU to PCI Bridge PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61AAA01&0&83 : VIA USB Enhanced Host Controller PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61AAA01&0&88 : VIA Standard PCI to ISA Bridge PCI\VEN_1106&DEV_B099&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : VIA CPU to AGP Controller 12 matching device(s) found. =========== USB devices =========== USB\ROOT_HUB\4&18F4B8E7&0 : USB Root Hub USB\ROOT_HUB\4&2F1C21A4&0 : USB Root Hub USB\ROOT_HUB\4&63B0842&0 : USB Root Hub USB\ROOT_HUB20\4&2A2E80A&0 : USB Root Hub USB\VID_04B4&PID_0033\5&8F113F9&0&1 : USB Human Interface Device 5 matching device(s) found.

I had the exact same problem! I solved it by downloading and installing the latest chipset drivers for the motherboard manually. In my case they were the latest Via 1 in 1 Hypersion drivers. You can find them here: http://www.viaarena.com/Driver/VIA_HyperionPro_V507A.zip My motherboard had a Kt266 chipset, what chipset does your motherboard have? Ruud

The updated drivers can be found here Maybe interesting to know, i installed the driverpack cd on a pcchips M811 v3.1 motherboard a few days ago and the driverpacks detected the soundcard as a Realtek AC'97 for Via soundcard. But strangely enough it didn't BSOD, even in device manager no exclamation marks or other errors where detected. Yet no sound was comming out of the speakers. I checked everything, nothing was muted, everything looked absolutely fine. I solved the problem by installing the above mentioned latest Via vinyl drivers manually.

If i understand correctly you are not using an unattended(automated) XP CD with the driverpacks. Your Atiide2k.sys BSOD was actually solved in driverpack base V5.11.6. So therefore, why not start using those driverpacks and create your own fully automated Windows XP installation CD and never be bothered with driver installations again? You'll be amazed how easy it is. You can do it manually by following the instructions at this page : http://www.msfn.org/board/index.php?showtopic=57201 Or you can use the powerpacker tool which will do everything for you: http://unattended.msfn.org/unattended.xp/ Please us know the result, by replying in this topic. We are still very interested in some more confirmation that this Atiide2k.sys BSOD is now completely solved! Ruud

Version: A3.81 Upload Time: 2005/12/26 Link: http://www.realtek.com.tw/downloads/dlac97...8&Software=True

You can downoad them from here : ftp://download.nvidia.com/Windows/81.98 Let's hope that these drivers are less buggy. Ruud

Actually there maybe a chance that there is something we can do against realtek. For example the portcls.sys problem. What it comes down to is that the existence of the realtek ac'97 soundcard still causes BSOD's on other manufacturer's Soundmax hardware. Isn't screwing up other manufacturer's hardware because of faulty realtek drivers a direct violation of the microsoft driver signing policy? Maybe we could threaten the company to release proper drivers within one week or else we go to microsoft and have them kicked out of the driversigning program? Ruud

@Jeet, have you been using the driverpack Monitor? Ruud

@Major 1. Was there no filename (like for example portcls.sys) mentioned in the BSOD message? 2. Did you try the unattended installation again, but without the driverpack sound A? 3. Have you already tried to take out the SB live? 4. Could you somehow get into windows en post the hardware id's of your system? You can download a little program to save your hardware id's to a file right here: http://www.driverpacks.net/Downloads/save_hwids.exe Please post the resulting file in this topic. Ruud

i am very curious about the result Ruud