Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

41 Excellent

About deomsh

  • Rank

Profile Information

  • OS
  • Country


  • Country Flag

Recent Profile Visitors

2,855 profile views
  1. While in Win9x there many Windows browsers usable, for Windows 3.1 this is not true. In my experience best is Netscape 3.04, but browsing is only more or less comfortable with a webproxy like proxycrime.com. I tested Links 2.21 for dos in a Windows 3.1 MS-DOS window, and I think this is possibly an asset for Windows 3.1 browsing. Also the video possibilities are great. While using a XGA 640x480 16 colors driver, inside Links for dos 1600x1200x16M32 (full color!) is no problem with the right video card /monitor. DPMI is delivered by Windows, if mouse-services are a problem a compatible mouse driver can be loaded in Real mode before Windows is booted (in my case CTMOUSE.EXE is not compatible with Windows 3.1, but LMOUSE.COM gave no problems with my USB-legacy mouse). Links for dos can also be used as a viewer for htm (I assume html = htm in 8+3 Short File Names), jpg, png, gif, but NOT bmp. With FileManager the neccesary associations with LINKS.BAT can be made (LINKS.PIF gives LINKS working in text-mode only for me). To get this result I am using following LINKS.BAT in my system: C:\DOS\LINKS\LINKS221.EXE -mode 1600x1200x16M32 %1 LINKS.BAT is most convenient placed in the Windows directory. LINKS.PIF can be made and edited (seems not critical). If used, better disable Alt+Enter and Alt+Tab (Switching to other programs works for me only if Links video-mode is exactly equal to Windows video-mode). I was surprised that a real packet driver (RTSPKT.COM for my RTL8139 NIC) together with WINPKT.COM is working in a Windows 3.1 MS-DOS window, this after the problems with Win9x.
  2. @Wunderbar98 Thanks @sweaterfish did a good job, he solved most of his problems with the 16-bits HDA2.DLL. I still hope he will publish a final configuration-file for Thinkpad X61, so I have less work next time. I am lucky you won't go further with packet driver networking in a MS-DOS window. Lately I solved the bootup problem on my H61-motherboard by adding DEVICE=C:\WINDOWS\NDISHLP.SYS in CONFIG.SYS (see the earlier described Netbind-setup), AND adding to PROTOCOL.INI: [ndishlp$] DriverName=ndishlp$ Bindings=XXXX$ (for XXXX substitute the name-part of the NDIS2-drivers file-name). With this addition my NDIS5-driver is still installed according to Network Neighborhood, but will not load if NETBIND.COM has been running before Windows starts. Only the NDIS2-driver seems to be used in this case, also while connecting to the internet with a Windows browser. Choice can be easily introduced with Menu items in CONFIG.SYS/AUTOEXEC.BAT
  3. Running Links for dos in Real mode MS-DOS will be faster at least (so far). Just for the record: I do not consider myself as a Win9x driver expert. My driver experiments are all about using 16-bits drivers in a Win9x environment. Still needed if there are no native Win9x drivers available.
  4. So far I have experimented with four NIC's: RTL8139C, Accton EN1207D, Compaq NC3121 (PCI-cards), and RTL8168 (onboard). For the Realtek NIC's there is only a NDIS2-driver available for use in Win9x). The other two cards have Win9x-drivers too. I found running NDIS2 + packet driver shim's inside a MS-DOS window NOT possible with Win9x-drivers installed (on my second test-motherboard Windows 98SE even refuses to start in case of the NETBIND-setup). But both Win95 drivers have the possibility to switch to their 16-bits NDIS2-driver (using the Adapter-properties in Network Neighborhood). After a full reboot PROTOCOL.INI in the Windows directory can be edited to add the packet driver binding (same as earlier). By trial and error I found that DIS_PKT.DOS (or DIS_PKT9.DOS) can be loaded by editing the Transport-key in the Real Mode entry in the Registry. Just search for Transport and add ",dis_pkt.dos" to the value of the key (without qoutes, the comma is the separator). Further DIS_PKT.DOS must be copied to the Windows directory. Afterwards a full reboot is needed! In this setup there are no NDIS-related lines in CONFIG.SYS anymore. In AUTOEXEC.BAT Windows Setup will add C:\WINDOWS\NET start WINPKT 0x60 (same value as used in PROTOCOL.INI) should be added AFTER the "NET start" entry (is working on two motherboards). If you want to try: I found a Win95 Linksys-driver with (as it seems to me) the same possibility: http://www.opendrivers.com/download/driver-14852.html (LNE100TX.INF -signature="$WINDOWS 95$"- in lne100w2.exe, only the backup server is still working).
  5. Last week I tested a real packet driver, available for a RTL8139 NIC: RTSPKT.COM. The packet driver is NOT working in a MS-DOS window! So it seems only the NDIS2-driver setup with the two shims DIS_PKT.DOS (or DIS_PKT9.DOS) and WINPKT.COM is possible. Which is sad, because the real packet driver is about 50% faster in Real mode MS-DOS! I searched the 'whole' internet to find a solution, but find nothing regarding running a real packet driver in a MS-DOS window. So, even wanted, no assistance available.
  6. Just like Arachne 1.97, I found Links-2.21 is running in Windows 98SE MS-DOS window (mouse services and DPMI are already delivered by Windows). Needed: a packet driver setup. Further the virtual packet driver WINPKT.COM, must be loaded AFTER the Real mode packet driver is loaded, but BEFORE booting Windows. At last WATTCP.CFG, placed in the Links-directory. Values needed in WATTCP.CFG can be found in Real mode with help of DHCP.EXE, coming with the mTCP-suite (see @Wunderbar98's other thread). First: SET MTCPCFG=[drive:][path]TCP.CFG (normally same directory where DHCP.EXE is located). Than copy SAMPLE.CFG to TCP.CFG. The line packetint should have the right interrupt, if not set earlier to another value, normally packetint 0x60 Only static IP's are working in a DOS window. A good domain name server should be added, I found fastest. My WATTCP.CFG (bold=local LAN-specific values!) ----------------------------------------------- WATTCP.CFG ----------------------------------------------- my_ip= netmask= nameserver= nameserver= gateway= ----------------------------------------------- Really amazing is that almost all video modes are possible in a DOS window, even with the Standard VGA 640x480 16 color driver! With my 1920x1200 LCD, highest mode possible in LINKS.BAT is 1600x1200X16m32 (my monitor refuses 1920x1200!). Speed is much lower than in Real mode, but for many sites acceptable. During scrolling through a webpage, pictures are loaded in the background. So not really disturbing (except wallpaper-sizes). First time: just run LINKS.BAT, later LINKS.PIF will be found and can be edited.
  7. @Wunderbar98 nice the setup is working for you. Sorry to hear about your low speed, with both DOS-setups. I tested DIS_PKT9.DOS too, no difference on my system. After downloading 33MB of the 100MB.ZIP, Links reported an average speed of 180KB/sec. But my ISP seams to be faster than yours, in Windows 10 & Firefox I downloaded the file with 7MB/sec (on another machine). I can't explain the difference with Windows 98SE & Opera 12.02. I found another nice speedtest loading pictures. If I change the homepage in LINKS.BAT to https://www.reuters.com/news/pictures it took 5-6 seconds from start to the OK-message in Links. During the loading of the 2.4MB I saw Links reporting speeds up to 800KB/sec. The pictures seems to be on different servers.
  8. In a MS-DOS window Arachne can't connect to the Real mode packet-driver, unless a virtual packet-driver is installed (installation in Real mode too, before booting Windows - same intvec as the real packet driver, so in most cases the command will be: WINPKT 0x60). WINPKT.COM delivers virtual mode packet services. Arachne will find now a packet-driver, with the Arachne packet-driver setup. That's all, no external TCP-stack needed, further just like in Real mode! Can't find my setup anywhere - connecting Arachne to a virtual packet-driver in a Win9x MS-DOS window - it's experimental. The famous Winsock 3.0 TCP uses WINPKT too. Winsock is still no-nag shareware, but WINPKT.COM is free - as far as I know. Arachne really needs browsing with a web-proxy like proxycrime.com. Without you're lost. Most stable without pictures; pictures sometimes seem to load indefinitely. But after fizzling with the Setup options, things are much better. Posting on msfn goes through a textbox with nice green fonts. No such limits like Links-2.21. By the way: I found Links-2.21 is running in a Windows 98SE MS-DOS window too, needs more modifications. I will report in your Links-thread when I'm finished.
  9. I can't compare, but downloading with Links-2.21 in dos with NDIS2+shim is about 200KB/sec. In my Windows 98SE setup, where I have to use NDIS2 for RTL8168 (only NDIS2-driver possible, no shim involved of course) my download speed with Opera 12.02 is about 450 KB/sec. I use always following url for testing: http://speedtest.tele2.net/100MB.zip
  10. Test: posting with Arachne 1.97 with help of proxycrime.com Running in a fullscreen Windows 98SE DOS window. Needed a DOS packet-driver as described by Wunderbar98. Further "WINPKT.COM 0x60" (no quotes) loaded before Windows starts.
  11. MSClient is needed to provide Network services like TCP/IP. Not needed here. The MSClient-installer has a bug, to connect to the internet additional files have to be copied manually (I learned the hard way during a project to connect Windows 3.1 to the internet using MSClient). You can test the packet driver on your NIC if there is a NDIS2-driver available. Don't forget to REM-out your current packet-driver in LINKS.BAT. PROTMAN.DOS is using 6KB conventional memory, DIS_PKT.DOS 3KB and my NDIS2-driver 42KB. NETBIND.COM is unloaded afterwards. By the way, your color-setting gave a scrambled screen on my 24" 1900x1200 LCD, but 1024x768x16m32 is quite acceptable for pictures. Regarding load-speed: on my Gub4Dos Memdrive loading CONFIG.SYS and AUTOEXEC.BAT took 4 seconds, 2 seconds for LINKS.BAT up to the homepage.
  12. I am using RTGND.DOS, with other NDIS2-drivers I believe only the file name has to be substituted everywhere (untested)! Relevant entries (directory as you like) -------------------------------------------------------------- CONFIG.SYS -------------------------------------------------------------- . . DEVICE=C:\DRIVERS\NDIS2PKT\PROTMAN.DOS /I:C:\DRIVERS\NDIS2PKT DEVICE=C:\DRIVERS\NDIS2PKT\RTGND.DOS DEVICE=C:\DRIVERS\NDIS2PKT\DIS_PKT.DOS . . . -------------------------------------------------------------- -------------------------------------------------------------- AUTOEXEC.BAT -------------------------------------------------------------- C:\DRIVERS\NDIS2PKT\NETBIND.COM . . REM AFTER YOUR PATH STATEMENT (PATH ...., or SET PATH=.... ) set Path=C:\DRIVERS\NDIS2PKT;%PATH% . . -------------------------------------------------------------- -------------------------------------------------------------- PROTOCOL.INI -------------------------------------------------------------- [protman$] DriverName=protman$ [RTL8168] DriverName=RTGND$ Medium=_auto Interrupt=11 IOBase=0xe800 [PKTDRV] DriverName=PKTDRV$ IntVec=0x60 ChainVec=0x65 BINDINGS=RTL8168 -------------------------------------------------------------- In PROTOCOL.INI instead of [RTL8168] AND BINDINGS=RTL8168 the right NIC-code should be used twice, but is not necessary in my opinion, as long they are identical. Needed is to substitute the name-part of the filename of the NDIS2 driver in DriverName=RTGND$ ($ at the end, no extension!). Do NOT change the [PKTDRV] entries. For other NDIS2 driver-specific entries needed in PROTOCOL.INI study the INF/INI/NIF-files coming with the NDIS2-driver, or take a look in %WINDIR%\PROTOCOL.INI if NDIS2-driver is installed in Windows 9x (for my NIC RTGND$ uses: Medium=_auto / Interrupt=11 / IOBase=0xe800). Shim in use is DIS_PKT.DOS 4733 Bytes 05/01/1998 The files PROTMAN.DOS and NETBIND.COM are part of MSClient. How to get them and the shim see: http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_NDIS_driver_installation Although the wiki states otherwise, the PROTMAN.DOS /I switch, pointing to the directory where all files reside, is needed - in my setup at least. BTW: don't install MSClient. Further: I am not sure if the path-entry is needed, my setup is already 2½ years old. Update: the PATH-entry isn't needed on my system!
  13. Nice! Because my (BIOS Legacy USB1.1)USB flash drive was a bit slow, I tested running from a 420MB 502MB Grub4Dos Memdrive. With LINKS.BAT loadtime for duckduckgo homepage is only 2 seconds. Do you want me to add my RTL8168 NDIS2/shim setup in this thread?
  14. @Wunderbar98 Thanks a lot, everything is working as expected. My only problem was the packet driver. My RTL8168 provides for a NDIS2-driver, but nowhere a packet driver around. Luckily I found an old Windows 3.1 project on my harddrive which uses a shim to connect to the NDIS2 driver. (-: Posted with Links-2.21
  15. @sweaterfish Thanks for testing. Setting only VolumeWidget in HDACFG.INI to $04 should give WAVEOUT.EXE full control. So the default of 48kHz is NOT the best choice. All in all the standard Output verbs sent by HDA2.DLL are the best choice. In that case their is no reason to maintain the $004-verbs in HDAICOUT.HDA and the Widget lines in HDACFG.INI can set to their original $04-values. Not only sound quality matters, the $011707C0 verbs is ment to activate the headphone amplifier needed to drive a low-impedance device (see the AD1984 datasheet). I don't know if their are any risks involved without, but that's all yours. I am not liable for it, I even never advocated use of HDA2.DLL! On my ALC662 codec (Realtek) enabling the headphone amplifier introduces noise, so I use 70740 only. Good! In my drawing the verbs for Aux are included (CD/DVD - not standard on Thinkpad X61 I believe, but an extension for the slim Ultrabay). On my system analog CD/DVD-audio redirected through the codec sounds much better than digital CD/DVD-audio. No, HDA2.DLL is playback-only by design. Although ADC can be enabled on the codec level and will be sent to the Azalia Link, nothing else will happen. The Runtime error you mentioned is the main reason to be very careful using HDA2.DLL. It can have very bad consequences. After a soft/hard reset Windows sometimes will use auto-scandisk. ALWAYS let the program finish and watch carefully SCANDISK.LOG afterwards. In general I don't agree switching Autoscan off in MSDOS.SYS. Scandisk is your best friend, but like best friends his comings and goings are not always desirable. Stability issues are reported while copying files together with audio playback. Also during simultaneous downloading of files and running DOS-boxes (the Windows command-line CONAGENT.EXE is involved too). But these issues are also dependent in de video card used! Know stability measures are: setting SYSTEM.INI [vache] MaxFileCache=1024 AND MinFileCache=1024, set [386Enh] MinTimeSlice=100. Also using SMARTDRV.EXE /X /L /V /B:57344 can be helpful (and speeds up file reading operations to compensate for the ultra low vcache setting - by design SMARTDRV.EXE can only be used on partitions 128 G(i)B max). During software installations / big copy-operations I always switch HDA2.DLL off with a semicolon before the HDA2.DLL wave(hda)-entrance in SYSTEM.INI and reboot Windows.
  • Create New...