Bryan thanks for your progress reports :-)
Nice to see how you have cartographed your local network, and that 
you're showing quite a bit of understanding.

Your existing autoexec looks pretty harmless to me.
I don't have any demands on what to put in there, that's why I didn't 
provide an example. Feel free to tweak the PATH variable to your 
liking. Let me know if you don't know what the %PATH% is good for. 
For instance, the pktdrv/start.bat modifies the %PATH% accordingly to 
fit its own needs = no need to do that in the autoexec.

Basically I'd say you're all set to try and load the DOS network 
stack, and see if that works :-) Again there are two alternative 
flavours of the DOS TCP/IP stack, one tastes of Microsoft, the other 
one of "independent open-source stuff" (the CRYNWR packet driver 
API). This is what you should try next - either A) or B), reboot 
inbetween A) and B) when you want to switch to the other:

A.) the one Microsoft way:

  cd msnet
  start
  ping 10.1.1.1
  ping 10.1.1.2
  ping 10.1.1.92

B.) the CRYNWR packet driver:

  cd pktdrv
  start
  ping 10.1.1.1
  ping 10.1.1.2
  ping 10.1.1.92
  
I suggest that you also try 
  mem /c /p
after A) and B) in turns for comparison. Look at the "largest 
executable program size" at the end of the listing :-)

If you get bored before I end up sending further "printing" 
instructions to you, try tcpdump or Wireshark on the Linux box :-) 
The output probably won't make much sense to you for a start, but it 
may open your eyes a little, to how chatty your local network is. 
Obviously plenty more info is available from me on that topic, and 
questions are welcome.
Only we're getting off topic in this list.

Maybe one small thing to test on your Ubuntu box: if you open a 
terminal window, and type 
    which lpr
what do you get?
If you get something like /usr/bin/lpr, could you also try this?
    which lpq
    lpq -a
Explanation:
lpr   is a command-line program that allows you to copy/send a file 
to a print queue, locally within your Linux box. The file = print job 
is expected at standard input.
lpq   is a print queue "manager" command, for your overview of the 
jobs being printed, and the queues present in the system.
Not sure if your CUPS comes with those utilities included.

Frank



_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to