Stas Sergeev
Stas Sergeev
You dont have to. The comments clearly say that you can map those to any drives. Map something to D-G and move dosemu2 drives to H etc.
I added the ability to create "holes" in the drive letters. Now you can do: `$_hdimage = "+0 -2 +1" to skip D and E at boot, and redirect them...
Well, this ticket is about migration guide from dosemu1, not a quickstart guide from zero.
Brief description/summary of NDIS driver properties: https://people.cs.clemson.edu/~westall/851/ndis.txt
> This doc has some diagrams not in the first doc, where it says "transmit chain" "Version 1.0.2 Preliminary Draft" No-no.
The direct link to your (outdated) doc though: https://ia801203.us.archive.org/15/items/bitsavers_3Com640600PreliminaryJan89_3419067/6406-00_Lan_Manager_NDIS_1.0.2_Preliminary_Jan89.pdf
> Unless I'm mistaken the only DOS application that requires an NDIS driver is MSCLIENT Yes, and unfortunately many people want to use msclient under dosemu2. Andrew even ported the...
A walk-through on implementing the NDIS driver: http://www.edm2.com/index.php/NDIS_Driver_Developer%27s_Tool_Kit_for_OS/2_and_DOS_-_Programmer%27s_Guide
https://github.com/OS2World/DRV-NET-Tigris/blob/master/NsmRes.asm Example of an ndis driver. Mostly in asm, but has a C headers with some structs to steal. :)
It seems, most of the complexity in the driver comes from the queued sending and lookahead receiving. But those are optional: we only need the synchronous send and full (no...