Jump to content

Petr

Member
  • Posts

    1,000
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Czech Republic

Everything posted by Petr

  1. You mean with NUSB not installed? No, this is not possible. It will work on Windows Me, 2000, XP and Vista, but not on older OSes. Petr
  2. What do you mean exactly? nUSB is not USB Controller driver but USB Storage driver. It is not dependent on your USB controller provided it is supported by your operating system (OHCI, OHCI Controller) or separate driver (EHCI controller). So you should not remove your USB controller driver, but the USB Storage drivers (if any) should be uninstalled and removed from the system. Petr
  3. The official resource is Microsoft Windows 98 Resource Kit, especially Chapter 4 - Automated Installations and Appendix D - Msbatch.inf Parameters for Setup Scripts. If you will use Google or search function of this forum you will find many topics like Unattended and Updated Boot CD for Windows 98, How to do it with code and links Petr
  4. Do you really think that there is something like "48-bit LBA capable chipset"? Petr
  5. So I have exported all registry entries after KB928388 applied and converted them to Windows 9x format and created both complete and update both reg and inf files, see the attachment: kb928388_9x.zip I don't know how it is with some timezones that use "Dynamic DST" sub-branch: Can Windows 9x use "Dynamic DST" information? Probably not. For some timezones "TZI" = "2007", but for some not. Any idea why? What should be added to Win9x servicepacks, TZI or "2007" contents? Petr
  6. I wrote some scripts or small programs in foxpro - the only language I know a bit. I'm also able to transfer localized portions of VXD files and 16-bit DLL/EXE files from old localized file to new updated file that it is in English only. It would be nice to have somebody who could write such tools with much higher professionality and much quicker than me. Regarding the most popular Windows SE servicepack, there was no update for almost a year already. Gape wrote me few days ago that he will wrote longer message so I will see. I think it would be much better to have complete list of necessary files for all (fe/se/me/95) servicepacks before localizing all files to all languages - because it not very good to go back and localize again different versions or additional files. It would be hard work anyway. Unfortnately I see not many people wanting to work on the new servicepacks. Petr
  7. And what about this change of dialing rules? http://www.msfn.org/board/index.php?s=&amp...st&p=522114 Petr
  8. English Q311561: 5266 dw 258 54b8 dw "IOSYSMSG", 258 Dutch Q311561 - mine 5266 dw 26a 54ca dw "IOSYSMSG", 26a Dutch Q311561 - your 5266 dw 26a 54ca dw "IOSYSMSG", 258 Dutch - original 5256 dw 26a 54ba dw "IOSYSMSG", 26a The word after the ISSYSMSG string is the length of the localized block, but you have left the length of the English block here. The same for 11EA0h: 5347 FA14 "SG.." 2f63eh: 5347 C400 "SG.." and 11EA0h: 5347 9F12 "SG.." 2f63eh: 5347 C300 "SG.." Regarding the remaining difference: 2F574h: 0600 1600 0001 C400 0000 1900 2B00 8900 A000 A900 AE00 "............+........." 2F574h: 0600 0A00 0001 B700 0000 1200 2500 8800 9F00 A800 AD00 "............%........." it seem you have left values valid for English version again. Petr
  9. I've discussed this topic here already: http://www.msfn.org/board/index.php?showtopic=76654 but nobody was interested in it. Petr
  10. As it was several times mentioned here, Microsoft put US English IO.SYS (WINBOOT.SYS) files to all language versions of Q311561 based on US English code. Apparently Chinese (Simplified), Chinese (Traditional), Japan, Korean, Arabic and Hebrew versions are correctly localized and Thai version is in English even in the original Windows because it is "Enabled" only. Now I have localized remaining updates, just moved the strings from original files to the Q311561 update: Brazilian Czech Danish Dutch Finnish French German Greek Hungarian Italian Norwegian Polish Portugal Russian Slovak Slovenian Spanish Swedish Turkish Please let me know if everything is OK. There may be one problem, even in originally localized files by Microsoft. There are three sections containig localized strings, the first and the second (that contain most of the strings) start at 16-byte page boundary so there are correct for sure. But the third, small part does not start on 16-byte page boundary and the system how offsets are calculated is different for US English version and for localized versions. In US English version the offsets are relative to 16-byte page boundary after the real start of the localized resources, while the offsets in the localized version is relative to the real start of the localization block here is the example. The first column is relative position to the beginning of the localized strings, the second colum is the offset from the beginning of the WINBOOT.SYS file. Original Windows 98 SE US English version: 2F4AE DW 0006, 000A, 0100, 00B1, 0, 12, 25, 88, 9F, A8, AD 0000 2F4C4 DB "None of the above", 0 0012 2F4D6 DB "Enter your choice:", 0 0025 2F4E9 DB "Windows cannot determine what configuration your computer is in.", 0D, 0A "Select one of the following:", 0D, 0A, 0D, 0A, 0 0088 2F54C DB "Original Configuration", 0 009F 2F563 DB "Undocked",0 00A8 2F56C DB "Dock",0 00AD 2F571 DW "MSDCMMSG", 00C3 00C3 = 2F571 - 2F4AE, but what means 00B1 as the fourth word? Only if you consider as a start not 2F4AE, but the second 16-byte boundary after this real start, then: 2F571 - 2F4C0 = 00B1 Original Windows 98 SE Czech version: 2F4AE DW 0006, 0016, 0100, 00B0, 0, 10, 1F, 73, 8A, 93, 9A 0000 2F4C4 DB "Nic z uvedeného", 0 0010 2F4D4 DB " Zadejte volbu:", 0 001F 2F4E3 DB "Nelze zjistit konfiguraci tohoto systému.", 0D, 0A "Vyberte jednu z následujících voleb:", 0D, 0A, 0D, 0A, 0 0073 2F537 DB "Originální konfigurace", 0 008A 2F54E DB "Mimo dok",0 0093 2F557 DB "V doku",0 009A 2F55E DW "MSDCMMSG", 00B0 2F568 (padding) 00B0 = 2F55E - 2F4AE, the same number is both as the fourth word and at the end of the localization block. This rule is valid for all 19 languages with except of US English. Q311561 US English version: 2F574 DW 0006, 000A, 0100, 00B7, 0, 12, 25, 88, 9F, A8, AD 0000 2F58A DB "None of the above", 0 0012 2F59C DB "Enter your choice:", 0 0025 2F5AF DB "Windows cannot determine what configuration your computer is in.", 0D, 0A "Select one of the following:", 0D, 0A, 0D, 0A, 0 0088 2F612 DB "Original Configuration", 0 009F 2F629 DB "Undocked",0 00A8 2F632 DB "Dock",0 00AD 2F637 DW "MSDCMMSG", 00C3 2F637 - 2F574 = 00C3, but this time is the fourth word 00B7. Why? Only if you consider as a start not 2F574, but the 16-byte boundary after this real start, then: 2F637 - 2F580 = 00B7 So the correct contents of the fourth word is unknown. As well as the correct contents of the second word, it is 0010 for US English and 0016 for all other languages. I'm not sure if these wors are used anywher at all so maybe it is absolutely irrelevant to try to figure out what are the right numbers. But if anybody encounters any problem with displaying the right message when using the notebook docked or undocked we know what to check. In that case pleae let me know and I will try to find the right solution. Q311561 WINBOOT.SYS files are identical for both Windows 98 (Gold) and for Windows 98 Second Edition. Unfortunately I have no idea how to localize Windows Me WINBOOT.SYS and WINBOOT.EBD files - all text resources are packed with code and compressed so the only way would be to find out how to uncompress this part of the WINBOOT.SYS file, localize it, and then to pack it again. Petr
  11. I've found a bug in wextract.exe in Slovak and Slovenian languages, correctd.
  12. The list at http://www.nvidia.com/object/81.98_9x_supported.html is not correct, much better is to use the list in the INF file posted by MDGx And just a note, according to http://download.nvidia.com/Windows/81.98/8...lease_Notes.pdf just AGP versions of 6xxx are supported, not PCI-E versions. PCI-E and AGP versions have different PCI ID. I have forced Win98SE to use this driver with some PCI-E graphics boards (6200, 6200 with Turbo Cache, 6600) and it worked. Petr
  13. There are no nv4_NV3x, nv4_MB_NV3x and nv4_WSApps_NV3x_DOEB sections in the W9x 81.98 inf file so it has no sense to add any of the a.m. lines. Petr
  14. If I remember correctly one simple test of JSCRIPT.DLL and VBSCRIPT.DLL functionality is to use Windows Update. It does not work with files that are in mesp at present. Petr
  15. Better from Windows 2000 SP4 but nobody succeeded yet. Petr
  16. This is standard Nvidia WHQL 81.98 Win9x driver downloaded from nvidia.com, please read the list of supported types above - there is no 7xxx type. Or you can read the Release Notes: http://download.nvidia.com/Windows/81.98/8...lease_Notes.pdf Petr Accoring to the Release Notes 6600GT (AGP) is oficially supported by Nvidia. Petr
  17. There are no drivers for these new boards, e.g. for the SATA controller so it is no chance to install Windows Me on this machine - maybe in some compatibility mode with significantly redced performance. But Intel made boards are extremely hostile to old OSes. If you really insist on Windows Me and you don't have license of Windows 2K/XP, you can use any Linux distribution with Vmware Server, it is free of charge, and you can run Windows Me inside Vmware. If you have Windows 2K/XP license, you can run Windows Me inside of Microsoft Virual PC 2004 SP1, it is free of charge too.
  18. As you may see at http://www.nvidia.com/object/81.98_9x_supported.html Nvidia does not have any Win9x drivers for 7xxx and 8xxx series. Petr
  19. The problem is with the package on MDGx site, the check for files is broken, it is [FileSectionList] 1=#S\BROWSEUI.DLL:6.0.2800.1106-6.0.2800.1892:%Warn2%:Ok 2=#S\CDFVIEW.DLL:6.0.2800.1106-6.0.2800.1612:%Warn2%:Ok 3=#S\IEPEERS.DLL:6.0.2800.1106-6.0.2800.1535:%Warn2%:Ok 4=#S\INSENG.DLL:6.0.2800.1106-6.0.2800.1475:%Warn2%:Ok 5=#S\JSPROXY.DLL:6.0.2800.1106-6.0.2800.1549:%Warn2%:Ok 6=#S\MSHTML.DLL:6.0.2800.1106-6.0.2800.1562:%Warn2%:Ok 7=#S\MSRATING.DLL:6.0.2800.1106-6.0.2800.1623:%Warn2%:Ok 8=#S\MSTIME.DLL:6.0.2800.1106-6.0.2800.1538:%Warn2%:Ok 9=#S\PNGFILT.DLL:6.0.2800.1106-6.0.2800.1506:%Warn2%:Ok 10=#S\SHDOCVW.DLL:6.0.2800.1106-6.0.2800.1892:%Warn2%:Ok 11=#S\SHLWAPI.DLL:6.0.2800.1106-6.0.2800.1740:%Warn2%:Ok 12=#S\URLMON.DLL:6.0.2800.1106-6.0.2800.1573:%Warn2%:Ok 13=#S\WININET.DLL:6.0.2800.1106-6.0.2800.1560:%Warn2%:Ok but should be [FileSectionList] 1=#S\BROWSEUI.DLL:6.0.2800.1106-6.0.2800.1895:%Warn2%:Ok 2=#S\CDFVIEW.DLL:6.0.2800.1106-6.0.2800.1895:%Warn2%:Ok 3=#S\IEPEERS.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 4=#S\INSENG.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 5=#S\JSPROXY.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 6=#S\MSHTML.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 7=#S\MSRATING.DLL:6.0.2800.1106-6.0.2800.1895:%Warn2%:Ok 8=#S\MSTIME.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 9=#S\PNGFILT.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 10=#S\SHDOCVW.DLL:6.0.2800.1106-6.0.2800.1895:%Warn2%:Ok 11=#S\SHLWAPI.DLL:6.0.2800.1106-6.0.2800.1895:%Warn2%:Ok 12=#S\URLMON.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok 13=#S\WININET.DLL:6.0.2800.1106-6.0.2800.1579:%Warn2%:Ok I also don't know for what reason was changed the content of the _sfx_manifest_ file, to maintain the format of the last official cumulative update it should look as follows: [Deltas] "RTMQFE\browseui.dll" = "browseui.dll._p", browseui.dll "RTMQFE\cdfview.dll" = "cdfview.dll._p", cdfview.dll "RTMQFE\danim.dll" = "danim.dll._p", danim.dll "RTMQFE\dxtmsft.dll" = "dxtmsft.dll._p", dxtmsft.dll "RTMQFE\dxtrans.dll" = "dxtrans.dll._p", dxtrans.dll "RTMQFE\iepeers.dll" = "iepeers.dll._p", iepeers.dll "RTMQFE\inseng.dll" = "inseng.dll._p", inseng.dll "RTMQFE\jsproxy.dll" = "jsproxy.dll._p", jsproxy.dll "RTMQFE\mshtml.dll" = "mshtml.dll._p", mshtml.dll "RTMQFE\msrating.dll" = "msrating.dll._p", msrating.dll "RTMQFE\mstime.dll" = "mstime.dll._p", mstime.dll "RTMQFE\pngfilt.dll" = "pngfilt.dll._p", pngfilt.dll "RTMQFE\shdocvw.dll" = "shdocvw.dll._p", shdocvw.dll "RTMQFE\shlwapi.dll" = "shlwapi.dll._p", shlwapi.dll "RTMQFE\urlmon.dll" = "urlmon.dll._p", urlmon.dll "RTMQFE\wininet.dll" = "wininet.dll._p", wininet.dll [Verify] "RTMQFE\browseui.dll" = AAB0216720CE6F2FD56B599AA25FC434 "RTMQFE\cdfview.dll" = D8DCD53E724F01A41098DC04936E1B83 "RTMQFE\danim.dll" = A6C450948A2223D95D7768BE7C0A57DF "RTMQFE\dxtmsft.dll" = C0B8F9A41A0275BA5DDF95061EDA8700 "RTMQFE\dxtrans.dll" = BE6F413D7A7FA0121082CB8CD97F53B6 "RTMQFE\iepeers.dll" = 5FF258CBFDAF0D3DDCA7B171E932E808 "RTMQFE\inseng.dll" = 8EB28D22111076C2F75291B373612493 "RTMQFE\jsproxy.dll" = F8E1794152BDE21DC7B9710510BA76C5 "RTMQFE\mshtml.dll" = 961597DCFCDB53772B8ACFCCE97A5970 "RTMQFE\msrating.dll" = CE2B73EA35CBE9E27F2DE5781CF3163E "RTMQFE\mstime.dll" = C94413E9E490AFF11C3F41741E0E82AC "RTMQFE\pngfilt.dll" = BF4A9D9A469FA75CC47E96463D2744E0 "RTMQFE\shdocvw.dll" = 5E2C35C2A714A1E7AB26852B437CC423 "RTMQFE\shlwapi.dll" = D25DB81D8A7F842350908CF129B90EC5 "RTMQFE\urlmon.dll" = 11149968DEB73015BCD192811AFA4D61 "RTMQFE\wininet.dll" = 1BA4B82D79375DD552289EA58A030FA8 [Delete] "*._p" And also this section of the INF files (both GDR and QFE) was not updated, the correct content is: Compversion = 28001895 Compid = Q922760 CatalogFile = Q922760.cat IEVersion = 6.0.2800.1106 Version = "6,0,2800,1895" Guid = {7d16667b-0ff7-4c6b-9fcf-775578e89cc2} And what means this added code? HKCR,"CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}",,,"Window List in Shell Process" HKCR,"CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}\InProcServer32",,0x00020000,"%11%\SHDOCVW.DLL" HKCR,"CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}\InProcServer32",ThreadingModel,,Apartment HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",,,"%COMPID%" HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",IsInstalled,0x10001,01,00,00,00 HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",Version,,"%VERSION%" HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",ComponentID,,"%COMPID%" HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",PackageVersion,0x00010001,3 It is not part of any original INFs? Petr
  20. Yes, Gigabyte GA-K8VM800M-RH contains VIA K8M800 chipset as well and I believe more in Gigabyte, but it is everybody personal preference. I see no reason not to use SATA HDD bigger than 137 GB, you do, Roman? Petr
  21. It does not look very good. 945G chipset - my INFs will be needed but - integrated graphics - no Win98 driver from Intel, you may get 2D driver from http://my.scitechsoft.com/ - USB 2.0 - no Win98 driver - Sound - Realtek ALC883 - no Win98 driver - SATA controller: no Win98 driver, can work in combined PATA compatibility mode, but not all BIOSes enable to set this mode, some of my Gigabyte boards yes, my MSI and Intel boards no, has to be verified - LAN Controller Realtek 8110SC: driver is here: ftp://202.65.194.18/cn/nic/PCI_InstallShield_5649_061019.zip - Radeon X800: Catalyst® Version 6.2 for Windows ME has beta support only, I have experienced some problems with PCI-E video cards with 256 MB RAM One comment - D945 is cheap but power hungry processor, you may consider some Core 2 Duo unless you have your own power plant. Petr
  22. If this mean Netvista (as you wrote here) 6266 then your drivers are here: http://www-307.ibm.com/pc/support/site.wss...cid=MIGR-4RZ2LT DriverVer = 08/01/2000,5.12.01.3000 http://download.boulder.ibm.com/ibmdl/pub/...ta/d64z14us.exe DriverVer = 08/01/2000,5.12.01.3003 http://download.boulder.ibm.com/ibmdl/pub/...on/d64z18us.exe DriverVer = 08/01/2000,5.12.01.3011 http://download.boulder.ibm.com/ibmdl/pub/...on/d69z28us.exe DriverVer = 08/01/2000,5.12.01.3029 http://download.boulder.ibm.com/ibmdl/pub/...on/d64z21us.exe DriverVer = 10/16/2001,5.12.01.3037 http://download.boulder.ibm.com/ibmdl/pub/...on/d64z24us.exe Full package: DriverVer = 10/16/2001,5.12.01.3037 http://download.boulder.ibm.com/ibmdl/pub/...n/dsiz14usa.exe (This version is probably the latest with support of 82801AA southbridge) Both IBM and Compaq have very good archive of all drivers. Petr
  23. OK, this is the important information. AD codecs use SoundMax drivers, they are OEM specific and not available from Analog Devices, just from the motherboard manufacturers - and you have not mentioned it yet. For example, all of these drivers are SoundMAX drivers for AD codec with 82801AA AC'97 controller: http://www-306.ibm.com/pc/support/site.wss...ocid=MIGR-43318 http://www-306.ibm.com/pc/support/site.wss...cid=MIGR-4R9SWY http://downloadmirror.intel.com/df-support...DM3030D_SM3.exe But I'm not sure if they work just with AD1881A chip and with your motherboard, every motherboard has its own ID and these drivers support the following ones (for 82801AA): d69z28us.exe %*WDM_AC97AUD.DeviceDesc%=WDM_IBMTWST, pci\ven_8086&dev_2415&subsys_016A1014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMTWST, pci\ven_8086&dev_2415&subsys_01861014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_01691014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_01991014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_01B11014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2415&subsys_01C61014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2445&subsys_01C61014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2415&subsys_01CD1014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2445&subsys_01CD1014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_01DA1014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_01DE1014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBMZEUS, pci\ven_8086&dev_2415&subsys_02031014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2415&subsys_02141014 %*WDM_AC97AUD.DeviceDesc%=WDM_IBM_RIO, pci\ven_8086&dev_2415&subsys_02151014 ven_8086&dev_2415 means Vendor ID 8086 = Intel, Device ID = 2415 = 82801AA subsys_016A1014 is Subsystem ID, 1014 is Subsystem Vendor ID, 1014 is IBM, 016A is ID of some specific IBM product. WDM3030D_SM3.exe %*WDM_AC97AUD.DeviceDesc%=WDM_CAYMAN, pci\ven_8086&dev_2415&subsys_59418086 %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_42418086 %*WDM_AC97AUD.DeviceDesc%=WDM_OTRIGR, pci\ven_8086&dev_2415&subsys_4F528086 %*WDM_AC97AUD.DeviceDesc%=WDM_CAYMAN, pci\ven_8086&dev_2415&subsys_43418086 %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_41538086 %*WDM_AC97AUD.DeviceDesc%=WDM_BRCHWD, pci\ven_8086&dev_2415&subsys_42578086 %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_47538086 %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_42508086 %*WDM_AC97AUD.DeviceDesc%=WDM_SMATRA, pci\ven_8086&dev_2415&subsys_53558086 %*WDM_AC97AUD.DeviceDesc%=WDM_FRBNKS, pci\ven_8086&dev_2415&subsys_46428086 %*WDM_AC97AUD.DeviceDesc%=WDM_EASTON, pci\ven_8086&dev_2415&subsys_45418086 %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_9019107B %*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415&subsys_1400107B %*WDM_AC97AUD.DeviceDesc%=WDM_FRBNKS, pci\ven_8086&dev_2415&subsys_1401107B %*WDM_AC97AUD.DeviceDesc%=WDM_GARBLD, pci\ven_8086&dev_2415&subsys_47428086 %*WDM_AC97AUD.DeviceDesc%=WDM_EASTON, pci\ven_8086&dev_2415&subsys_424E8086 Subsystem Vendor ID 8086 = Intel, 107B = Gateway Intel uses two letters identification converted to hexa code in the Subsystem ID, it means: 4241 = BA = BA810 (Baton Rouge) 4F52 = OR = OR840 (Outrigger) 4341 = CA = CA810 (Cayman) 4153 = AS 4257 = BW = BW810 (Birchwood) 4753 = GS = GS810 (Great Smokey) 4250 = BP = BP810 (Black Pine) 5355 = SU = SU810 (Sumatra) 4652 = FB = FB820 (Fairbanks) 4541 = EA = D815EEA (Easton) 4742 = GB = D850GB (Garibaldi) 424E = EN = D815EEA2/D815EPEA2 (Easton 2) This is specific to specific manufacturer and therefore is so hard to find the right SounMAX driver if you don't know the motherboard manufacturer and type. Petr
  24. What version of Everest do you use? I remember that the old versions did not displayed this information, I use the latest one (3.50.xxx). For my controller the first build showing the correct information is 2.451 1.51.195 to 2.20.444: --------[ PCI / PnP Audio ]----------------------------------------------------- Intel 82801DB ICH4 - AC'97 Audio Controller [B-0] PCI- not useful information 2.20.451 to 3.50.792: --------[ PCI / PnP Audio ]----------------------------------------------------- Realtek ALC650 @ Intel 82801DB ICH4 - AC'97 Audio Controller [B-0] PCI- useful information Petr
  25. This is incomplete information, there should be something like: --------[ PCI / PnP Audio ]---------------------------------------------------------------- Realtek ALC650 @ Intel 82801DB ICH4 - AC'97 Audio Controller [B-0] PCI in the Multimedia section. Petr


×
×
  • Create New...