ruudboek

Most likely this is caused by the fact you have a soundmax compatible soundcard in your pc and no specific soundmax compatible driver is available in the driverpack sound. There is currently a problem with the Realtek ac97 drivers which confict with soundmax compatible soundcards. The confict is the following : When no drivers are available for a soundmax compatible soundcard, hardware detection will start to use the Realtek ac97 drivers for some still unknown reason. Ofcourse this would be the wrong driver and when Windows XP tries to startup after the hardware detection phase, the BSOD with the portsys.cls error is the result. This problem has been around for 1 year now. You can basically do 2 things to solve this problem : 1. Have BTS add the driver to his driverpack sound. You should use this program and post the resulting file so that BTS can add the HWID to the Sound Driver Pack. To prevent this BSOD as much as possible, the driver pack Sound needs to contain as much soundmax compatible drivers as possible. So please do post your hardware ID's. Also it would be nice if you could post a link to the site where your drivers can be downloaded. 2. Remove the Realtek drivers from the driverpack sound. If you want a solution right now and want the installation to continue without the BSOD, take the following steps to remove the conflicting realtek-drivers from the driverpack sound : 1. Extract the driverpack sound with 7zip. 2. Delete the \S\R folder. 3. 7Zip all the folders with maximum compression (archivename has to be the same as the name of the driverpack sound). 4. After the installation you will ofcourse have to install the missing driver for your soundcard manually. B.t.w. can you please confirm if these steps prevent the BSOD? We want to be certain that deleting the Realtek drivers solves this nasty problem. For more information see also this topic :http://www.msfn.org/board/index.php?showtopic=30389&pid=408003&st=250entry408003 Ruud

@mjc. Or, if you want a solution right now and want the installation to continue without the BSOD, take the following steps to remove the conflicting realtek-drivers : 1. Extract the driverpack sound with 7zip. 2. Delete the \S\R folder. 3. 7Zip all the folders with maximum compression (archivename has to be the same as the name of the driverpack sound). Can you please confirm if these steps prevent the BSOD?

Ok, then why don't we set those realtek-problem-drivers apart and have them installed later, at GuiRunOnce? I was thinking of the following (will most likely only work when "new hardware found" pops up if no realtek driver has been installed) : 1. Rename the \S\R folder to \S\REN so hardware detection will no longer find the realtek drivers which cause the portcls.sys BSOD. 2. Delete all driverpack folders accept for the \S\REN folder during CMDLINES.TXT instead of during BTS_DPsC.cmd. 3. Rename \S\REN back to \S\R as the next step in CMDLINES.TXT. 4. In my experience Windows will remember all references defined in OemPnPDriversPath, i presume the same counts for the references to the driverpack folders. If this is the case it will mean that the first time Windows XP starts up, the "new hardware found" will pop up, but will then not ask for drivers, instead it will start using the Realtek drivers from the \S\R folder. Regrettably i have no experience with realtek ac 97 soundcards. Maybe someone can confirm if "new hardware found" really does pop up when no drivers have been found for the realtek ac 97 soundcard? Ruud

Hello all, i just went through this now one-year-old BSOD-topic completely. Can i savely conclude that if we want a fool-proof driverpack sound which will NEVER cause a portcls.sys BSOD, we have to remove the folder \S\R (the Realtek ACM 97 drivers) from the driverpack sound? Or would this NOT be sufficient and should the D\S\SM folder (SoundMAX and Sigmatel drivers) also be removed? Ruud

Hello Coconut, This is great stuff, its the missing piece in the puzzle! Do you already have the fixed .exe available? Ruud

@Bashrat To my suprise both windows XP aswell as the driverpacks do not support the good old Diamond Viper II Z200 or the S3 Savage 2000 Videocards. I found the latest driver which supports both the Viper II aswell as the S3 Savage 2000 on the following website : http://www.savagenews.com/?action=articles...cle=7&section=1 On that website i chose the Savage2000 Win2K/XP Driver 9.21.01G (latest version)which works like a charm. This is the Hardware ID of my Diamond Viper II Z200 : PCI\VEN_5333&DEV_9102&SUBSYS_59541092&REV_02\4&21093523&0&0008: S3 Savage2000 Hope you can add it to your next Driver pack Graphics release ( will test it for you right away ) Greetings, Ruud

Downloads work like a charm again. Thanks Bashrat

Well, this post alone made me solve the error on 3 different HP pc's : http://www.msfn.org/board/index.php?showto...ndpost&p=309202 Those 5 inf files alone support 13 different HP models. What i mean to say is that since the last driver pack sound B came out (april 19th), quite a large list of compatible devices have already been posted. Because of this, my curiosity for an upcomming release is very much aroused Ruud

Hallo Bashrat, Firstly, i would like to say that your driver packs are the most usefull things i have found on the internet in years. This is a trully revolutionary concept! i have seen the portcls.sys error on quite some machines now. AC97 chipsets are apparently extremely popular. Looking at the topics involving this error, i was able to add drivers to the driver pack sound and solved this error by doing that. If i understand correctly, the real problem is that, if there is no driver available for a AC97 (soundmax) compatible soundcard, the installation will crash with a blue screen showing the portcls.sys error. This is very disturbing for the installation, because if you want the installation to proceed without going through the hassle of finding the correct sounddrivers, updating the driverpack, then updating the unattended installation, burning the cd, etc, the most efficient way to go is simply doing the same installation again, but then with an unattended cd which does not include the driverpack. In practice, what it comes down to is that i have give out 2 cd's to make certain that the installation will finish properly. For these reasons i would be very interested in some method to prevent this blue screen error. If there really is no solution for this, i would be very interested in a new driver pack sound which is updated as much as possible, so this error is avoided as much as possible. Are you planning on releasing a new sound driver pack any time soon? Ruud

Does this release support ATI mobility?

Hello Bâshrat, When are you going to create the last driverpack, the chipset driver pack? Ruud

SCAN=0 UPDATE=0 ICON=0 Worked like a charm. Thx all, really appreciate this.

Hello all, i am trying to get Bitdefender standard 8.0 silent, but the old switches from Bitdefender 7.2 do not seem to work. The old switches are : msiexec /i "r:\bitdefender\bdstandard.msi" /qb- REBOOT=Suppress' Regrettably the silent install stops after doing a automatic scan for virusses. You then have to click on "Close" to make it proceed.