First post, by xeon3d
Hey!
I bought a couple of ebox 3300MX's some time ago and I was thinking they'd be really cool Win98 Machines.
As such I've been getting it running properly, and the result is two drivers that are now on GitHub, source and binaries, MIT licensed:
https://github.com/Xeon3D/Vortex86MX-Win98
Video: RDC M2010 (PCI 17F3:2010)
Based on JHRobotics' excellent VMDisp9x VESA driver, with native M2010 support added on top:
- 2D engine acceleration for solid fills, screen-to-screen copies, pattern brushes, text backgrounds and rectangles
- Hardware mouse cursor (the M2010's MMIO cursor, 64x64 ARGB)
- DirectDraw page flips synced to vertical retrace (no more flicker in full-screen DirectDraw)
- Refresh rate selection in Display Properties (60-85 Hz, from the option ROM tables)
- Monitor power-off (DPMS) for screen saver / power management
- Full-screen DOS boxes (Alt+Enter) and "Restart in MS-DOS mode" work, including the font and palette
Modes are still set through the VESA BIOS, so it's 8/16/32 bpp from 640x480 to 1280x1024.
Ethernet: RDC R6040 (PCI 17F3:6040)
RDC's own RDCPCI5.SYS for Win98 hangs the machine at "Windows is shutting down". R6040.SYS is a from-scratch NDIS 3.0 miniport that replaces it:
- Shutdown and restart complete normally
- ~3.5 MB/s down, ~5-6 MB/s up over FTP (32 MB round trips, byte-identical)
- Media sense, auto-negotiation retry, a small DOS tool that reads the driver's shutdown log from CMOS (the eBOX has no COM port)
For comparison, RDC's Windows 2000 build (11.14.08) also turns out to work on Win98 at the same speed and restarts cleanly, if you prefer a vendor driver.
Download
Releases page: video build 33 (full install package, Have Disk -> RDC-M2010.INF) and network 2.0 (see README.TXT; it can be swapped in under an existing RDC install so your TCP/IP settings stay). Every earlier test build is kept as a pre-release, in case anyone wants to A/B something.
Known issues / notes
- Restart can freeze in real mode if the two USB 2.0 (EHCI) controllers are enabled under the NUSB USB stack. That's NUSB, not these drivers. Workaround: disable the two "Enhanced Host Controller" entries in Device Manager (USB 1.1 keeps working). This alone took a *LOT* of time.
- The hardware cursor can't invert the screen, so the text I-beam is drawn in software.
- DirectDraw itself is JHRobotics' VMHal9x (prebuilt); the 2D engine isn't used for DirectDraw blits yet.
- Everything was tested on one eBOX-3300MX. Reports from other Vortex86MX boards are very welcome.
Development was done with Claude, with all testing on the real hardware by yours truly. RDC's open-source Xorg driver was the register reference.
Feedback, bug reports and test results welcome, here or, preferably as GitHub issues.