Arachne at FreeLists---The Arachne Fan Club! You can disregard all of that stuff. All you need is tha 'ready to go' rtspkt.com Simply use the command line as indicated in my origianl post. At the dos prompt..... rtspkt.com 0x60 That's it.... that's all you need to do. On Thu, 23 Oct 2008 07:01:34 +0930, Greg Mayman wrote: > On Mon, 20 Oct 2008 20:26:19 -0500, Glenn McCorkle wrote: >> It looks like the packet driver you need is already in my D/L dir >> http://www.glennmcc.org/download/rtspkt.zip > The file unzipped without problems, but I am confused by some of the > things I have to edit in RSTPKT.TXT. For example: > ;************************************************************************ > ; Put your Vendor ID and Device ID > ;************************************************************************ > 7419 2 ech,10h; Vendor ID > 7416 2 39h,81h; Device ID > From the boot hardware data, my Vendor ID = 10ECh, and my Device ID = > 8139h. Now I'm guessing the part of those lines after the the "2" is > LowByte, HighByte, in which case it is correct. > ;************************************************************************ > ; Put your Vendor ID and Device ID of CardBus > ;************************************************************************ > 7629 2 ech,10h; Vendor ID > 7626 2 38h,81h; Device ID > CardBus? I have a CardBus? If so, how do I find its Vendor ID and Device > ID? I'll leave it unchanged and see what happens. > ;************************************************************************ > ; Put your driver name here (no delimiter) > ;************************************************************************ > 4c7c 8 'RTSPKT',0h; > 7204 8 'RTSPKT',20h,20h; > I guess they mean the name I will choose when I execute > "rtpatch rtspkt.com rtspkt.txt <put driver name here>" > But > ;* !!! NOTE: DO NOT USE THE SAME DRIVER NAME AS THE ORIGINAL > ;* DRIVER!!! > So I had better think of another name than RTSPKT. I'll try MYRTSPKT. > Nope. That gives a "string too long on MYRTSPKT" error... funny, there > is space for 8 characters... I'll try PKTDVR.... > Ah, yes, that's better. I copied the resultant file PKTDVR into the same > subdirectory as SSH2DOS. The sample command line called up by SSH2DOS /? > does not show how to tell it where the packet driver is located and what > it is called. I'll have to look further into it when I have more time. > But for now I'll look more at Personal Netware to see whether I can > follow the 12 pages of directions I found in DOSBOOK. -- Glenn http://www.delorie.com/listserv/mime/ http://www.delorie.com/djgpp/doc/msdog.html http://www.glennmcc.org/ http://www.law.cornell.edu/constitution/constitution.table.html Arachne at FreeLists -- Arachne, The Premier GPL Web Browser/Suite for DOS --