#BUY DOS2USB WINDOWS#
So now, as far as Windows is concerned, the network is not only clocked in, but willing to work overtime if neccessary. Anybody out there remember the PWS on Win95? (that’s personal webserver – and you could even do ASP on it) Packets basically travel up and down the TCP/IP stack through the adapter and get fed right back to you. Testing network functionality in the absense of a live network.
#BUY DOS2USB SOFTWARE#
Sure enough, it’s still around in XP.įor the kids out there, the Microsoft Loopback Adapter is basically a software based network adapter that simulates a live network. Five or six years ago that would have been the first obvious solution. LOOPBACK ADAPTER it flashed across my mind. I put the issue aside for a few days but it was always nagging at my mind and then one day my wet-ware mainframe finally dredged up something from the archive. It’s funny the things you forget about or at least put into the deep-archive, tape backup of the mind. This, as you are no doubt thinking, is a less than an optimal solution. Windows doesn’t care if there are other computers to talk to on the network, so long as the network has punched in and is on the clock. My initial solution to at least get the new store up and running was to simply give them a small 4 port hub to plug into. It doesn’t matter that the shared printer is connected to that very machine because as far as Windows is concerned it’s on the network and the network has packed it in. But once you disconnect the network cable, the network goes away and so does your shared printer. Where I happened to have the POS computer plugged into the network to load the software and apply updates etc. Odd that.īut what do you do when you don’t have the printer connected to the parallel port and you’re in a stand-alone type of scenario? Now, the first thought you have is that you’ll just share the printer and then use the old NET USE command to capture the printer port and map it to the USB printer. In XP you have to know the NET USE command to make it go as the GUI interface disappeared. Prior to Windows XP you can just go into the printer properties and there’s a little button there to capture the printer port and map it to a network printer. Even if you want to use a network printer it’s dead simple. What I forgot about was the fact that DOS doesn’t know a gosh darn thing about USB. When it came time to buy some more, I chose to go with the USB interface rather than parallel because hey, it is the 21st century after all. Very nice little units that were fairly reliable. We used the nice little T-88’s from Epson. When you sell stuff, you need to give out receipts. In my previous job I had the great misfortune of having to support a DOS based point-of-sale application.
That’s not really all that tough and actually got me thinking about a similar experience I had recently. Scott Hanselman has a post on his weblog about getting a shared network printer to work in DOS. Hi check this: HOWTO: Print to a USB Printer from DOS in Windows XP
0 kommentar(er)
