Networks, printers, and DOS, oh my!

[superdave76]

Ok, here's the setup: My brother-in-law's small business has 2 computers connected by a crossover cable. Computer A has a DOS-based inventory database on it and has an HP Deskjet printer connected. Computer B is sharing the HD from Computer A and is running the same database program from that hard drive, so there is just one database. Computer B also has a dot-matrix printer attached to print multi-copy invoices. Computer B, while running the program from Computer A's hard drive can print to the dot-matrix, but Computer A can't. (the printer is shared)

I know that DOS requires an LPT1 or LPT2 for printing, and I captured LPT1 for the dot-matrix on computer A, but still no printing AND the deskjet quits working. If I configure it for LPT2, it won't print on either computer. The deskjet needs to stay connected to Computer A for UPS shipping label printing, and he'd like to get both computers to somehow print to the dot-matrix from the DOS program.

Does anyone have any suggestions on how to set this thing up so that this will work with minimum cost and minimum complications? (Print server was tossed around but is probably not feasible/affordable.)

Thanks for reading.

 

[JustinLerner]

Hey Dave tell your brother to bite the bullet and make the upgrade. The cost isn't as great as you think, but may be more time consuming.

Businesses really only survive if they make the investment plunge at certain times. If they can't do so, even though the investment cost may be more than they think they can or they refuse to do so, the businesses tend to suffer and are less able to compete effectively.

A print server from Linksys like the EFSP42 has two LPT parallel bi-directional ports and four Ethernet 10/100 ports for devices. It costs around $130 with shipping. Although LinkSys doesn't specify that it provides DOS support, it does support NetBEUI, IPX and TCP/IP protocols. To configure it, if you continue to use DOS, connect another PC with Windows to the switch, install the Admin software on Windows and then set the appropriate network protocol and settings so that networked devices in DOS can use the switch (like make sure they have the same netmask and subnet if using TCP/IP).

Since your DB application is probably DOS specific and maybe even proprietary, it might not work in any other setting than DOS only configuration. You don't say if the DB app is proprietary and if it's able to function with it's printer via a network, but if it's old enough it might be more difficult to make the DB print to a network printer, although it still seems wise to pursue an upgrade process after evaluating the program capabilities (configuration and settings) and the network limitations of your DOS DB.

The DOS memory management model is very poor and even running the database and program from a DOS 'shell' window in Windows NT 4 (off a FAT16/32 disk if necessary) would be better than running it from DOS. Since your PC's are probably quite old, NT 4 is best (it works on 486's and higher CPU's with as little as 32MB RAM), but the hardest to find. New configurations should always be tested first on a test platform if possible (or image the DOS system, directories, structures and DB to another drive and then try imaged drive on another PC.)
Since your program has two users via DOS, it doesn't sound like it is really multi-user aware. Investing in a multi-user version makes sense if you plan to do any significant work with the software.

 

[JackMDS]

In theory I agree with Justin Lerner.

If the upgrade rout is impossible, it can not be done by using Parallel Port sharing box.

Something like this.

BI DIRECTIONAL AUTO SWITCH 4-1/1-4, AS-8144B.

There are different combinations of this Gizmos, call them to find the right one.

 

[ScottMac]

What kind of networking / stack is loaded to allow the two computers to talk / share?

Was it working and just quit, or did it stop after some change in the system?

In the "olden" days, the printer / LPT assignment had to be done before the network stacks were activated and sharing enabled. Check the load order of your config.sys elements and the executables in Autoexec.bat.

Are you getting any errors at boot time? Does the computer / application THINK it's printing OK? or does the job just sit in some queue somewhere? or does it return an error?

Have you tried the printer on some other system to make sure it's not the problem? have you tried any other printers on that interface (parallel port)?

Gotta know.....


Scott