Jump to content

xrayer

Member
  • Posts

    233
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Czech Republic

Everything posted by xrayer

  1. I finally found why Win9x couldn't boot from devices attached to SATA3 port, see the bottom of my post here.
  2. Hi, after a day messing around I finally managed Win98 USB 2.0 to work. I went to backup of my W98 install on old P31 board, copied in all machine*.inf files and let redetect the HW again. What a surprise, both EHCI, root hubs and generic hubs was detected fine but I got a BSOD after detection of SB audigy. When I disabled it the USB 2.0 works fine (with existing nUSB 3.3d I used before). Even the plugged devices was automatically detected in systray! I got high speed about 18MB/s when copying from USB flash, fine... But no sound, this suxx... So I give one more try, again restore the backup, infs and redetect. It seems that the process is a bit random like Win98 plays Motne Carlo with me (and the PnP). This time the USB stuff was detected fine, Soundcard was detected fine but I was unable to install NDIS driver for ethernet adapter RTL8111E (that worked for me before). When I browsing devmgr I didn't see any resource conflist but found that one EHCI has shared IRQ with the eth.NIC. So I tried to disable this EHCI and after some further messing I was finally able to install DOS NDIS driver and use it with Windows (it may have worse performance than 32b native drivers but still fine for normal browsing). If I reenable the second EHCI it worked for a while but I got a BSOD soon so I kept it disabled. So finally I have most of peripherals working as expected, summary: USB 2.0 - works 1/2 of available ports (only one EHCI active but at high speed and autodetection) Sound - works with SBA2 native drivers HDD/DVD - works with standard IDE controlled, speed is OK as BIOS supports DMA network - limited support of RTL8111E by DOS NDIS driver but fine for general use VGA - 7900GT/256M with latest nvidia beta drived works fine as before Here's my fully expanded devmgr tree "screenshot". The only remaining issue is that I cannot boot Win98 from my SSD attached to SATA3 port. It was discusses in this thread I found that it's caused by BIOS bug or rather BIOS simplification of DMA logic that doesn't properly suports DMA on SATA3 ports in v86 mode. It hangs on any write disk access. And as Win98 switches to v86 mode and tried to write to disk it hangs. This effect also happen under DOS if some advanced memory manager like JEMM/QEMM/EMM386 is loaded and switch CPU in v86 mode. I found that it can be cured by installing J.R.Ellis DMA driver before or just after loading the memory manager and DOS then can write to SATA3 attached disk fine. But unfortunatelly this driver is not compatible with Win9x due to some Windows bugs and it only boots to desktop where explorer.exe crashes immediatelly. So as a workaround I moved my Win98 installation from C: (SSD, primary partition) to D: (HDD, primary partition) and then I need to run BIOS boot manager at boot to choose HDD to boot. It then become C: so no need to change paths and Windows boots fine. But it swap also some other driver letters that are not so important at this time for me. Would the R.Loew SATA patch be related to this issue? I think that it would need a windows native SATA driver that will take DMA control over BIOS but intel didn't released any for PCH chipsets for Win9x of course. Maybe someone could write a drived based on UniATA opensource but I don't know how much are the disk driver models different from NT and how much effort it would be, probably unreal...
  3. Interesting, I didn't know that's possible to run some DOS command after shutdown. Is is possible also with automatic windows start? If I will call win.com explicitly in autoexec.bat will it then continue next lines after shutdown? There's FDAPM utility by Eric Auer, that can shutdown a PC both APM/ACPI ways. If no APM detected then it parse ACPI table to learn how to shutdown it. The command is fdapm /poweroff Unfortunatelly due to latest unofficial nvidia drivers bug the windows doesn't reach the shutdown screen so I use reboot instead. If I want to shutdown automatiucally I create a flag file before reboot, then reboot windows at some event and when it boots again I check the presence of flag file on C:\ and if the file exists I will delete it and perform fdapm /poweroff. As flag file was deleted it will boot normally on next power on...
  4. Here is my SETUP screen: There are 3 USB related options 1st enable/disable EHCI (if disabled it's not visible also under windows) 2nd enable support for USB keyboard legacy function (AFAIK it's done as SMM routine to be transparent to OSes but it's often buggy). I intentionaly use both PS/2 KB & mouse to avoid need of this 3rd enable support for USB storage (probably via INT13h extension) so e.g. DOS can access and also boot from it. I have enabled only the 1st option. The issue I previously mentioned with XP was not related to this BIOS options. I just wanted to note that I have to manually disable the USB hub power saving mode because XP couldn't power on it automatically. And I guess that Win98 may have similar problem but I don't know if such power saving function is enabled (or what is the default state) when USB INF or nUSB is installed.
  5. Yes, I have normally USB Legacy Storage Support disabled, I only enable it when I need to boot from USB flash. Maybe the problem have some clue to USB power saving mode of USB ports - I had also problem with USB ports in WinXP that when I didn' have plugged any USB device during boot then it couldn't be detected later. But if I plugged them before boot it worked at high speed. Then I found that I need to disable USB power down of every 2 USB root hubs in device manager (the last tab). Maybe Win98 is also not able to succesfully power on USB ports automatically when some device is plugged in (power down feature may be enabled in chipset by default)... PROBLEMCHYLD already offered me his USB stack from the nSP and I tried but worked even worse - it siledntly detected some device at boot (probably the 2nd hub) that caused BSOD and I couldn't skip it.
  6. I found on intel site version 9.4.4.1006 that contains more HW and 9.4.0.1027 https://downloadcenter.intel.com/download/24394/Chipset-Intel-Chipset-Device-Software-for-Intel-NUC-DE3815TY https://downloadcenter.intel.com/download/23061/Chipset-Intel-Chipset-Device-Software-for-Intel-Desktop-Boards They are not described to support XP but in readme it is and structure is same as older ones. This is probably why I failed to find it directly on intel's web but google showed... UPDATE: In my case I have no choice in SETUP to disable partial USB devices. Just enable or disable all. Maybe it could be achieved by manual messing with PCI config registers before Windows boot. Maybe Win98 PnP capabilities are exhausted to assign HW resources. I have similar problem on a notebook with PCMCIA controller where I cannot install PCMCIA disk driver otherwise I get BSOD. Under WXP it works, of course... I think using W2k driver would have better chances than Me as it's newer. I didn't tested W2k on my machine but I expect that when INFs are available for W2k same as XP, then it should work. Maybe it's needed to port more parts of W2k USB driver stack to W98 but wdmstub is little bit magic for me, I don't know it's capabilities.
  7. BTW I found newer intel INF package version 9.4.0.1026 (5.8.2013) for W2K-W8.x. I wonder why intel withraw this from his site and offer much older 9.2.0 from 2011. The current version 10.0 is only for W7-10 - so this mean intel condemned XP to death. We would need make some unofficial INf package for recent HW (like Skylake and future)...
  8. Thanks for the nUSB package. Today I made a new clean install (with himemx limit to 1GB) and used your INFs during 2nd install phase. It went as expected, most of devices was detected except USB EHCI that had "!" mark and some unknown PCI device that I already saw there in my older tests, probably nothing important. Then I installed nSP, removed 2 "!" marked EHCIs in safe mode and installed nUSB 3.5. After reboot it detected 2 EHCI, 2 USB 2.0 root hubs and 2 Generic USB hubs. Here arose the first problem. 1st Generic USB hub was installed OK (from USB2.INF) but the 2nd which followed makes Windows go BSOD. I repeated more times but it always lead to BSOD so I must skip this 2nd device. Afte boot when I go to devmgr and click Refresh the Generic USB hub was detected again, I must not to install it otherwise BSOD... But when I plugged the USB stick and skip that hub then Mass storage was detected and flash drive was detected succesfully. It took quite long time, about a minute. Then USB disk icon appeared in systray (of course not automatically, only when manual refresh). When I access the drive it's extremely slow. I copied a 0,5MB for more than a minute, commander show me ~6kB/s - LOL much slower than old floppy! But file was copied OK and was readable on other PC. So it works same crappy way like your X58. Here's my updated shot of devmgr:
  9. Hi, I added requested files to package, download it again http://http://rayer.g6.cz/1tmp/nusb35cz.zip The usb2.inf and usbstor.inf are from CZ nusb 3.3 pack. I think it's not necessary to keep them localized - this is only names of devices and don't affect windows GUI. As there's no longer CZ maintainer I think it's better to use english verison of inf fils that is up to date than old localized ones. Aha, I read that the remove of UHCI happened since P55 so I though X58 is affected too. But R.Loew made it working even on newer chipset than mine so it is possible... What is Automatic Skip Driver agent and how do I disable it during install? But it's not related to already installed system...
  10. I installed nUSB 3.5 and checked again that all files from the package are at the right place. Only a few of files are localized in CZ windows so I put them here: http://rayer.g6.cz/1tmp/nusb35cz.zip please can you make installer package of it? Unfortunatelly it still doesn't work. Here's my devmgr: I tried Refresh button after plug in but any new device didn't appeared in any section... Please upload a sshot of your devmgr on X58 to have better idea how it should look like. Is there some automatic tool that will carefully clean up any trace of previous nUSB from system, just to be sure if it doesn't interfere with some previous install. Probably I would need to try fresh install with your chipset infs and then nusb to prove it if the problem is not caused by some old config... BTW my USB stick has a LED that lights up when system detect it and communication is established. The LED blinks when system R/W the media. But in W98 it only blink for very short time when plugged in and doesn't light up. So it seems like EHCI/hub is not initialized.
  11. I checked USBD.SYS and it's on a place: C:\WINDOWS\SYSTEM32\DRIVERS version 4.10.0.2226, size 18944B I tried to get nUSB 3.5 from MSFN thread but the link on zshare seems so be dead. After some googling I finally founf eng. version here http://www.tmeeco.eu/9X4EVER/GOODIES/(there are also a lot of drivers that may be useful) I extracted the files and going to find matching cz counterparts. Is it possible somehow to run installation proces from directory with extracted files? There seems nothing like setup.exe or else to run (I extracted via Winrar)...
  12. Thanks, I'll check if USBD.SYS is on place. BTW I could upload CZ version of USB drivers and DLLs from CZ WinMe used by nUSB 3.6 but I don't have skills how to repack it as installer executable.
  13. I used nUSB 3.3d CZ before and then I tried nUSB 3.6 EN. Does the difference of USB 1.1 driver matter? I think not since I have no any UHCI. Is new nUSB still based on W2K USBSTOR.SYS? I think it is and it should matter for USB 2.0 systems. But I don't know Win98 USB and nUSB internals. I don't know clear how nUSB is dependent on Windows drivers and how much does it replace them. Maybe the problem is that device detection wizard and systray watcher is somehow linked to USB1.1 and if this subsystem is missing it doesn't launch. But how R.Loew did it? So there must be a way to link it with USB2.0 controller...
  14. Hi, I booted my Win98SE to safe mode, deleted old P3x inf files and put there your new INFs. I went to devmgr and deleted all USB controllers and devices, IDE controllers and some sytem devices linked to old P31 chipset. I rebooted and let the system redetect new HW. It automatically recognized and installed C200 USB 2.0 controllers and hubs. I have no "!" mark on any USB device but it still doesn't work. System doesn't detect any plugged USB device. I also reinstalled nUSB but same result.
  15. >LoneCrusader Thanks for the INF update, I'll try during weekend I'd like to put INFs into my existing installation so I will remove conflicting older INF for P3x chipset first... EDIT: INF thread is here
  16. I had a problem with setup.exe from Win98SE CZ install. It siletly exit - did nothing. I replaced it by setup.exe from WinME (or Win98FE) and installation process started as expected (of course I had setup himemx memory limit before).
  17. And what you exactly mean by "preload" ? You make your own installation CD that install this drivers during setup phase?
  18. How do you preload this driver? Is it done by nUSB or needed to do manually or via other inf? I have USBD.SYS present and it's referenced by other USB*.SYS drivers and USB.INF, IntelICH7USB.INF - maybe I need to update IntelICH7USB.INF to match PCI device IDs to my P67 PCH?
  19. Yes, I was learnt that USB 2.0 hub contains also speed translator so it can connect USB 1.1 devices. The main difference is that now all ports (and connected devices) goes through the hub and not directly to EHCI. BTW DOSUSB driver should handle this, it also detected mass storage device but failed later on acessing the drive letter. OK, this gives me a hope. I'll try to clean old nUSB and reinstall again. I'm just confused that there's no "!" mark in devmgr on any USB controller but it silently ignore plugged devices. I see only a short flash from LED on USB stick when plugged in. No new device detected, neither unknown device in devmgr... The question is if the unofficial nvidia driver core really contains some new code for 8xxx GPUs or if the lines in INF files was only added for future use/some testing but never released. Anyway 8xxx cards are now far obsolete too. Maybe it would be possible to compile some simple 2D accelerated driver based on Nouveau opensource driver for Linux but it would be still a lot of hardwork...
  20. >rloew I played with RTLNIC.SYS and SPLIT8MB a bit more (I used SPLIT8MB from before on my P31 system because I cannot boot without it). But in this case I found it goes a bit better when I commented SPLIT8MB out. Then I was able to boot with disabled NIC and enable it later after boot. It freezed computer for about 10-20s but then it started and NIC became operational, I did a few pings out. But after reboot it hanged again. So I would need to enable it on demand after boot and don't forget to disable it before shutdown. I also asked Realtek support if they will upgrade the W9x driver, just for fun But then I found another working approach. I observed in list of NIC drivers that Windows provide that I could use a 16-bit mode ODI or NDIS drivers. So I installed the RTGND.DOS via OEMSETUP.INF (the last version 1.52 from year 2015), it also added a line "net start" to my autoexec.bat that invooke RTGND.DOS loading before Windows start (it reports using 1Gbit link). Sure it would have worse performance than native 32bit driver but it works stable and speed is far as good for common browsing. I just tested DL from my hosting FTP and got about 750kB/s (not kb/s) so I'm happy with that. Only disadvantege seems to be little slower boot because it waits some additional seconds to initialize DOS driver. BTW I wonder why Windows are waiting so long if network is enabled. A clean install without net can boot in 10s but with net it maybe 30s or more... The bigger issue may be with USB. I read that intel dropped UHCI since it's 5-series chipsets so it wouldn't be possible to get even USB 1.1 slow speed. It also have some USB2.0 hub between the ports and chipset that behaves like a wall that any DOS USB driver can pass - I tried my favourite USBASPI.SYS - it detected EHCI and hub but failed to detect target device. This intel suxx ASPI Manager for USB mass-storage Version 2.27 (C)Copyright Panasonic Communications Co., Ltd. 2000-2008 Controller : 00-26-0 VID=8086h PID=1C2Dh (1458h-5006h) EHCI : MEM=FBFFE000h-FBFFE3FFh(1024Bytes) Controller : 00-29-0 VID=8086h PID=1C26h (1458h-5006h) EHCI : MEM=FBFFD000h-FBFFD3FFh(1024Bytes) ... Initializing Host Controller 1/2 ... ... Initializing Host Controller 2/2 ... ... Scanning USB Devices ... USB Device : VID=8087h PID=0024h HS(HUB) ... Scanning USB Devices ... : VID=8087h PID=0024h HS(HUB) ... Scanning USB Devices ... ERROR : Target USB device not found.1 char device installed.Driver loaded.I just tired to install nUSB 3.6 and it detected 6-series USB root hubs and I don't have any "!" mark in devmgr but any USB device plugged in is not recognized by system. Do you have working USB on your Z87 system? About SATA, yes I use my SMB utility to access HDD directly. I can force it to talk via 1F0 legacy port and it works. You can read various HDD info and SMART status with it. It's freely available at http://rayer.g6.cz/programm/programe.htm#SMB I did some upgrades but not released yet... >LoneCrusader Yes I read your separate thread about installation mod INFs. I wonder there's so stupid 64k limit from RM DOS era. Is there some #inclue directive like in C to include other files? I don't have any problem to select manually right INF for my system and copy it manually. But I would prefer to be able to use it also after install (I'd like to preserve my program setting that I tuned for years than throw it and do clean instal). I think I could copy selected filed to my INF directory before I move system from old PC to new PC and let it redetect new HW. I'm just waiting for better CPU and DDR3 to complete my new setup before I will defintely replace the MB then I'd really like to try your INFs About the patch - so it means that now with new memory patch it is possible to use any 7xxx PCI-E VGA with 512M? Wouldn't it also help with 8xxx cards? Seems that nobody succeed with them. Fortunately I have some spare 7600 and 6600 with 256 or 128M if my 7900 fails...
  21. OK, I found the Tenda driver RTLNIC.SYS of version 5.621.304.2005, size 73984B, I uncommented RTL8111 lines and installed it without problems but after reboot PC hangs. I have to go to safe mode and disable it in device manager. When I enable it in normal mode it hangs immediatelly. Is this the version that you tried? And on what HW did you tried it, D or E? How should I test if SATA is in legacy not native mode? What utility? I can see it can be accessed via legacy ports 1F0 like std. IDE...
  22. >LoneCrusader Plese could you send me your intel INF 9.4.0.1017 mod for personal testing as you don't have time to finish it? What "patches for the 7xxx" are developed? To fix the windows shutdown issue? I don't have any other problem with that latest unofficial drivers on my 7900GT. >rloew Did you investigate the differences between 8111B and E? I belive it would't differ much. I used older NDIS driver RTEND.DOS for DOS TCP/IP from 2011 and it works fine with 8111B and 8111E too. I tried to edit the INF file of latest Win9x driver (30.10.2008) and imported there 8111E specifics (chip revision 6 section, registry entries..) from the INF file of XP drivers. Win98 detected my 8111E but I got ! mark in device manager. I got also error 1F6 during installation of my modded INF. Then I tried to boot with RTENIC.SYS from older 2k/XP drivers (year 2009 - supp. 8011D and 2010 - supp. 8011E) it booted but still with ! mark. There are no HW resources conflicts. Maybe the Win9x RTENIC.SYS could be patched - if there is some chip revision check inside to bypass or so... I also got idea about HW chip downgrade (I work with QFN chips at work quite often but I can see that 8111E has different package and pinout that 8111B so direct replacement is not possible. Would you reveal what other driver you find to work? Limitation to 100Mbit absolutely don't bother me, the warning is problem but I'd like to test it. Yes I know that Win9x don't recognize AHCI (this should work now for NT4 with UniATA driver) and INT13h extension take place so Win98 can run via BIOS access - compatability mode. It means performance degradation but not so ugly, even when put on SSD... I belived that SATA3 (6 Gb/s) should be 100% compatible with SATA2 (3 Gb/s). The BIOS should provide SATA IDE legacy mode and SATA IDE native mode same way for both class of ports but it's not 100% well done. While NT4 or DOS doesn't see difference between ports Win9x see. I think that this may be problem of BIOS that doesn't setup SATA3 ports 100% correctly to legacy mode (maybe SMI IO trapping is involved) or it may be HW issue that SATA3 (at least intel's implementation) controller has some differences that cannot be configured by BIOS to 100% compatability mode. This is probaby also the reason why my previous experiment with Win98 on B75 board ~2 years ago failed - I also had connected the SSD on SATA3 port (of course)... It would be good to highlight this information someway here on forum so another experimentators wouldn't fall into the same trap (and save a day of endless reinstallations trials
  23. Holy f*ck! I just plugged my SATA HDD to another port and it works! Instalation process continued, detected devices, another reboot and wow, I have a basic working desktop. It boots within 11s (80GB older seagate, no SSD). Even I was able to boot my previous installation - it redetected the HW but there are left some issuses. USB seems not work at all and Realtek RTL8111E has conflict mark (it worked with older RTL8111B - I though it's just minor difference and drivers would work.). Anaway I'm happy with this limited functionality. What is the difference between SATA ports? Before the change I had it plugged to SATA3 port 0. And for some obscure reason, Win9x doesn't like SATA3 ports even if set to IDE legacy mode (for ports 0-3). Other 2 SATA2 ports works fine (the rest 2 are unavailable in IDE mode). What's interesting - it works in AHCI mode. If AHCI mode is selected, then AHCI PCI option ROM is activated and it take control of INT13h and I can then use any SATA port (yes, also SATA3) and Win9x boots from it. Here's summary: SATA3_0 = CH0, master (cannot boot Win98 in SATA native/IDE mode but can boot in AHCI mode) SATA3_1 = CH1, master (cannot boot Win98 in SATA native/IDE mode but can boot in AHCI mode) SATA2_2 = CH0, slave (can boot Win98 in SATA native/IDE and AHCI mode) SATA2_3 = CH1, slave (can boot Win98 in SATA native/IDE and AHCI mode) SATA2_4 = RAID/AHCI port 4 (can boot Win98 in AHCI mode) SATA2_5 = RAID/AHCI port 5 (can boot Win98 in AHCI mode) On current machine I have W98+DOS+NT4 on SSD primary partition 0, WinXP on SSD primary partition 1, linux on primary partition 2 + data HDD and I'd like to profit from SATA3 connection. So I would need to move W98 on data HDD or try AHCI way (but AHCI is problematic for direct access tools)...
  24. >Drugwash Yes, I already have GB P31 MB so I know CTRL+F1 trick. On this MB it onlu unhide one option - the PCI latency, thats's unrelated to this issue. I already set the BIOS much fail safe as possible, disables USB, HDA, NX, VTX, HT, set 1 core, sata IDE mode... >MrMateczko Well, it's positive that Win98 works on your i7 Haswell so newer CPU and chipset is no crucial problem (drivers will be but it's not fatal for bare system) >jaclaz Thanks for the documentation. I just tried both /p i and /p j options (2 installations) but seems no difference, always hangs after 1st boot. Also the bootlog looks very similar - the last line is a binary garbage all the time... See here: http://rayer.g6.cz/1tmp/GA-P67-DS3-B3/boot95.txt http://rayer.g6.cz/1tmp/GA-P67-DS3-B3/bootme.txt http://rayer.g6.cz/1tmp/GA-P67-DS3-B3/boot98pi.txt Anyone have a clue? It seems to die quite on early stage of boot, I doubt PnP/ACPI stuff plays role here...
  25. Yes, I limit the RAM via XMS and system.ini as standard process. In my BIOS I don't have any option to disable ACPI, you mean just use /p i switch? I didn't remember it and it's not listed by /? - a hidden feature? I can try again. Isn't ACPI stuff loaded later in 2nd phase of installation where PnP devices are detected (after reboot)? BTW I found this video (if not a fake) proving W98 run on core i7 3960X (AMI BIOS) https://www.youtube.com/watch?v=YOWzorOD-II


×
×
  • Create New...