From: lharr...@gmail.com   
      
   On Sunday, December 3, 2023 at 7:12:51 AM UTC-5, Christian Holzapfel wrote:   
   > lharr...@gmail.com wrote:    
   > > What are the chances of a DOS driver?   
   > The leaked sources for the original PCnet DOS packet driver are around.    
   > They are plain x86 Assembly, processed by    
   >    
   > # MAKE Version 3.6    
   > # TASM Version 3.1    
   > # TLINK Version 5.1    
   >    
   > Generally, the places such a driver needs modification to work with our 9-K   
   are well known to Ryan and me and properly documented now - but I'm not that   
   fluent in Assembly (yet).    
   > Furthermore, the DOS driver is working in 16-bit mode only, while the 9-K   
   ASIC and also the PCnet chip in our case need some 32 bit addressing.    
   > So it's a little more to it, but generally doable.    
   > Maybe in the boring, gray start of next year I could look into it.    
   > If someone else is willing to pick that up, I'm happy to help :-)   
      
   I've been pretty decent writing code for c# and such, but not sure if I could   
   pick this up and be useful.    I'd have to start reading about it and see.   
      
      
   As far as the 9x driver, I have been unable to get the updated driver working   
   at all.  Even with a fresh install of Windows 95.   I'll get an IP but can't   
   ping the gateway, the reply times out.  I didn't change any of the default   
   settings of the driver...   
    I think the buffer or whatever was set to RX + TX.   This weekend has been   
   bit busier than I expected and I have to run so.. not sure how much I can play   
   with it more this weekend.  Also... with the fresh install, the 32bit driver   
   for my BusLogic card    
   is intermittently loading... which what the hell?!?!  So I want to nuke the   
   install again and find a more trusted ISO of Windows 95 C.   Downloaded some   
   fresh copies last night and had one fail that it couldn't find a file in a cab   
   in the middle of the    
   install... turns out people commented on the download page that the ISO was   
   wonky.  I dont burn the ISO's to CD-R as ZuluSCSI will emulate them as a CDROM   
   if you put the ISO on the SDCard and name it properly.    
      
      
   Anyway, with the fresh install, performance was a tad better.   I truly think   
   the reply board is slow in general.  The 486 Overdrive 100mhz and Kingston   
   TurboChip also both score about the same as the POD83... which is 20% slower   
   than any rando board out    
   there that can take these chips.  I've had a few others with the Reply board   
   get the same results.  Not sure why.    
      
      
   TCP connection established ...   
   Receiving from client, packet size  1k ...  1267.69 KByte/s   
   Sending to client, packet size  1k ...  1425.52 KByte/s   
   Receiving from client, packet size  2k ...  1583.88 KByte/s   
   Sending to client, packet size  2k ...  1693.53 KByte/s   
   Receiving from client, packet size  4k ...  2123.17 KByte/s   
   Sending to client, packet size  4k ...  1846.58 KByte/s   
   Receiving from client, packet size  8k ...  2132.16 KByte/s   
   Sending to client, packet size  8k ...  1903.23 KByte/s   
   Receiving from client, packet size 16k ...  2304.99 KByte/s   
   Sending to client, packet size 16k ...  1941.89 KByte/s   
   Receiving from client, packet size 32k ...  2434.78 KByte/s   
   Sending to client, packet size 32k ...  1929.03 KByte/s   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)