ruudboek

Can someone else who has an nforce 3 or 4 chipset also confirm that using the older driverpack lan 5.10.1 solves the problem with the nvidia ethernet driver? Ruud

@Bashrat, ****, now you were faster then me @Maxximum, Maybe you can search for .dmp files on the c drive of the BSOD pc with a bartpe bootcd . Usually in those dmp files the complete BSOD error can be found. We just need to know if the 'nv4_mini.sys' is mentioned in the BSOD error. If only the driverpack graphics A is causing this BSOD, could you try the older version of the driverpack graphics A? If you still have it ofcourse. Ruud

Well then why don't give your solution a try on the driverpack unattended? You can add your modification quite easily to the driverpack Graphics B by following the following steps : 1. Extract the driverpack graphics B with 7zip. 2. Go to the extracted D\G\S3\1\ folder. 3. Make the modification to the S3T3D2X.INF. 4. 7Zip the D folder with ULTRA compression (archivename has to be the same as the name of the driverpack graphics B). 5. Do a new slipstream of the driverpacks. 6. Done! Post the results in this topic so BTS can make the same adjustment to the S3T3D2X.INF file. Ruud

@maxximum, This sounds very interesting, maybe there really are conflicting drivers! What was the exact BSOD error message? (looking for a filename) You should also try without the Chipset driverpack, but with the Graphic driver packs: BTS_DriverPacks_BASE_V5113 +DriverPack_CPU_V506 + DriverPack_MassStorage_V510 DriverPack_Graphics_A_V5101 + DriverPack_Graphics_B_V511 If there will be no BSOD in this case then we can conclude for sure that there is a confict between the chipset driverpack and probably the driverpack Graphics A (that one includes the graphic drivers for your Nvidia Geforce 7800 videocard). Ruud

@BigDaddy, regarding the nv-something BSOD on your hummer-lapop with the Nvidia Geforce 5500 FX Mobile, i have found another very recent post from Nakatomi2010 who got the following BSOD error with his Nvidia Geforce 6600 : DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS" nv4_mini.sys stop code: 0x000000CE (0xF6C3FAA0, 0x00000008, 0xF6C3FAA0, 0x00000000) Can you tell us if the BSOD error that you got on your hummer-laptop is the same? The post of Nakatomi2010 can be found here : http://www.msfn.org/board/index.php?showtopic=59132 If you have the same BSOD error, then it confirms that there are issues with the nvidia drivers from driverpack graphics A. We can then add your problem to that topic and try to find a solution together. Ruud

@BigDaddy, I think you are right on that. Never heard of an laptop with an Nforce chipset anyway. Then it must be the driverpack graphics A that causes this BSOD. Maybe you could try it again, *but* this time using the older driverpack graphics A. The driverpacks graphics A contain all the nvidia graphic drivers. We really have to track this BSOD down. BSOD's are really destructive to the driverpacks in my opinion, it makes them unreliable. If possible, could you maybe post the full readable errormessage in the BSOD? Maybe it sais something of the filename that is responsible for the BSOD. Ruud

I found the "NV something BSOD" also in this other (very recent) post : http://www.msfn.org/board/index.php?s=&sho...ndpost&p=416927 It looks like there are new BSOD problems introduced which are caused by the new DriverPack_Chipset_V511! Ruud

Heeeee i found the "NV something BSOD" also in this other (very recent) post : http://www.msfn.org/board/index.php?s=&sho...ndpost&p=417294 He solved the problem by using the older chipset driverpack ( DriverPack_Chipset_V5072.7z ). @BigDaddy : Does your hummer-laptop also have a nForce4 ultra chipset? Could your try to make a brandnew install, *but* using the DriverPack_Chipset_V5072.7z and post the results in this topic? @Bashrat : It looks like new BSOD problems are introduced which are caused by the new DriverPack_Chipset_V511! Ruud

@BigDaddy, i know an excellent way of troubleshooting your Herculus-Fortissimo-II-does-not-install problem. You could try to check that the hercules drivers from the new driver pack sound B are totally complete. In my experience, if as much as one file in missing in the driverpacks it will not install the driver at all. In order to test this, it could be a good idea to try to install the Herculus Fortissimo II manually, but then using the drivers from the driverpack B. Follow these steps to do so: 1. Extract the driverpack sound B in some directory on the machine with the Fortissimo II soundcard. Use 7zip for that. 2. Go to start/settings/control panel/system/hardware/device manager 3. Doubleclick on one the "unknown devices" (usually the ones with a yellow exclamation mark) which could represent your Fortissimo II soundcard. 4. Click on the tab "Driver". 5. Click on "Update Driver". 6. At he hardware update wizard, select "No, not this time" and click on Next. 7. Select "Install from a list or specific (Advanced)" and click on Next. 8. Uncheck "Search removable media (floppy, CD-ROM...). 9. Check "Include this location in the search:" and click on "Browse". 10. Now browse to the location where you extracted the driverpack sound B and then to the folder D\S\H\2. 11. Click on "Ok". 12. Click on "Next". 13. Now if the wizard will say "The wizard could not find a better match for your hardware than the software you currently have installed", it will mean that your specific Herculus Fortissimo II is not supported by the current driverpack sound B. In that case please post your hardware id's in this topic. 14. If, however the wizard says the it cannot install the drivers because a file is missing, please note down what file it is missing. It is possible however that more then 1 file is missing. In that case it will be necessarry that you put in your original Herculus Fortissimo II driver CDRom and copy the missing file to the D\S\H\2 folder and try again. Keep repeating this procedure untill the driver is installed completely. Don't forget to write down all files it still needs, then zip those missing files and post them in this topic. Ruud

Hello 5eraph, maybe you and Muiz should compare hardware id's. And it might also be interesting to check to see if all the hardware id's from Muiz are actually supported by the driverpacks. Ruud

I disagree! These driverpacks are very exciting indeed. To me it's about the biggest thing that can be found on the internet right now. I don't know if you realize it or not, but these driverpacks bound all these competing manufacturers together, yet only one installation CD will be sufficient for all. Windows is starting to get the same benifits as Apple has with its controlled yet very limited hardware variaty. Maybe some day, these driverpacks will be so big, that things are going to be the other way around. Then manufacturers will be have to pass the BTS logo to be driverpack-compliant. And then i am not even talking about the fact that with these driver packs there is now is a totally different approach to troubleshooting things. If you are being "bothered" by people with their computerproblems, just hand them over your installation cd and have them help theirselfs, hell you can make your installation so simple, even your granny can reinstall her own computer! That saves humongous amounts of time and gives you a new "first step" in troubleshooting which frees you from paying time consuming visits. (Resetting the computer to factory defaults sort of speak) Ruud

Hello Bashrat, You are very right on that. I've experienced this portcls.sys error on several HP machines and i got them all permanently solved by integrating HP drivers (5 inf files) in the drivers pack B which where mentioned in this wonderful post : http://www.msfn.org/board/index.php?showto...ndpost&p=309202 I assume that you are asking this because you are going to release a new Driverpack Sound B. Well in that case, i've reaaally been looking forward to that, because looots of people have been nice enough to post their missing soundmaxdrivers in the "portcls.sys error" topic : http://www.msfn.org/board/index.php?showtopic=30389 You can really find a huge number of "new" soundmax drivers there. Ruud

richardkohlsjr, are you also using method 1? Ruud

So the HDA PCI device problem is really solved by changing those lines? I think it is time for a new driverpack BASE then.

Hello fackamato , your post should not be in this topic because you are not using the driverpacks, but still, why don't you try and create an unattended installation with those wonderful driverpacks, then try my fix and then let us know if you get through the installation without experiencing the portcls.sys BSOD. We need more results people, keep posting! Ruud

That is completely correct Fencer128, you've got it right! I really think Realtek has bettered its life, the results so far seem to confirm that the portcls.sys BSOD missery is over! Please people, don't be shy, try my solution and KEEP ON POSTING YOUR RESULTS in this topic! It would also be very interesting if someone with an actual Realtek AC '97 soundcard could try this solution aswell, so we have some confirmation that the new Realtek AC '97 drivers DO install when they SHOULD install! Ruud

Ah yessss, like hell that it didn't work for you, it did work! You got rid of the portcls.sys BSOD and was therefore able to CONTINUE the installation so that you were able to install the appropiate driver manually! (otherwise you would still be looking dazzed and confused at this stupid bleu screen without being able to do anything about it The whole point of this topic is that we got rid of the portcls.sys BSOD! The portcls.sys BSOD will only occur when there is NO soundmax driver for your specific soundcard available in the driverspacks sound. The problem is that, when no soundmax driver is available, for some unknown reason, XP would start to use the Realtek AC '97 drivers instead of no driver at all, which causes the portcls.sys BSOD. So please DO post your hardware id's and a link to the location where your driver can be found so BTS can add them to his Driverpacks Sound. Ruud

Did you slipstream the driverpacks using the KtD (keep the drivers) method? Ruud

How stable is this driverpack TV? Are there any known cases of bluescreens (BSOD's) ? Who is the author of this driverpack and is there some website related to this Driverpack TV? Ruud

Hello BTS, I decided to create a seperate topic of this error, because there are now several problems addressed in the DriverPacks BASE V5.10.5 and it is starting to get confusing to me. The problem : i have tried your new Driverpack base v5.10.5 combined with all the other latest driverpacks. I am starting the XP installation from DOS, therefore using dosnet.inf. When the xp installation starts with the copying of the files (1st phase) i am getting the following errormessage : Setup was unable to copy the following file : PORTCLS.SYS. Now i noticed that portcls.sys was indeed not present in the i386 folder, so i guess this error is correct. Therefore i took a look in the dosnet.inf file and noticed that there where 2 references to the file portcls.sys. Then i deleted those entries and tried the installation again and it worked. The installation continued without the above mentioned errormessage. It looks like you overlooked these references in the dosnet.inf! Ruud Update : I also checked driver.cab and did found a portcls.sys file. I also found one in sp2.cab, but still no portcls.sys file can be found in the i386 folder after the slipstreaming. I did another test, this time only took out 1 portcls.sys entry from the dosnet.inf : [ForceCopyDriverCabFiles] ;portcls.sys Then tried the installation again, and yes this time no PORTCLS.SYS copy-error. Is this also a valid solution? Is anyone else starting the installation from DOS and experiencing this same error? Ruud

Hey Nakatomi2010, Please let me know by replying in this topic if this procedure will fix your portcls.sys BSOD problem. Ruud

Hello all, since it currently is a well known fact that most likely the portcls.sys BSOD error is caused by the presence of the problematic Realtek AC '97 drivers i took a look at the NEW Realtek AC '97 drivers Version A3.78. Basically i deleted the old Realtek AC 97 drivers from the extracted Driverpack sound A ( The realtek drivers are present in the D\S\R folder) and replaced them by the new drivers ( kept the Realtek HD driver though ) Then repacked the driverpack sound A and did a brand new slipstreaming of this driverpack and all the other (latest) driverpacks. Luckily i have an HP DC5100 computer on which the portcls.sys error will happen with the current driverpacks. I tried the new installation on the HP DC5100 and Guess what? It worked! Now i am 100% sure that on this machine and most likely all other soundmax-compatible machines this portcls.sys-error is caused by the Realtek AC '97 drivers currently included in the Driverpack sound A. I have also tried the installation without the AC '97 drivers and then there is also no portcls.sys error! Quite remarkable is that even though the driverpacks do not have the proper soundmax driver for the buildin soundcard available, after the installation in the device manager the soundcard is identified as some C-Media soundcard and it is accompanied by a Yellow exclamation mark. Can someone else also try to follow the same procedure and 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 16.9 MB (17,815,863 bytes) 2. Extract the downloaded WDM_A378.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_A378.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

Hello BTS, i can assure you that i do not have RyanVM's UpdatePacks in my unattended. I only have a standard Windows XP unattended with SP2 and mediaplayer 10. I have used YOUR Mediaplayer 10 slipstreamer to slipstream mediaplayer 10. Ruud

Hello BTS, as promised i have tried your latest driverpack graphics B on my pc with a ViperII Z200 (=S3 Savage 2000). The driver was not installed, instead the "new hardware found" popup came up after the installation. I extracted the D\G\S3\2 folder and directed the hardware found popup to that folder, it appeared that it still needed the following 2 files : NDL.DLL and S3UNINST.EXE So i added the 2 files to the the D\G\S3\2 folder and added that to a new driverpack graphics B. Then i tried the installation again and yess it worked! Could you please add these 2 files to your driverpack graphics B? I have added them as attachment to this post in zipped format. Ruud Removed the attachment.

Hello BTS, i have tried your new Driverpack base v5.10.5 combined with all the other latest driverpacks. I am starting the XP installation from DOS, therefore using dosnet.inf. When the xp installation starts with the copying of the files (1st phase) i am getting the following errormessage : Setup was unable to copy the following file : PORTCLS.SYS. Now i noticed that portcls.sys was indeed not present in the i386 folder, so i guess this error is correct. Therefore i took a look in the dosnet.inf file and noticed that there where 2 references to the file portcls.sys. Then i deleted those entries and tried the installation again and it worked. The installation continued without the above mentioned errormessage. It looks like you overlooked these references in the dosnet.inf! Ruud