Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Paradox 4.5 conversion from Novell to Win2K

Status
Not open for further replies.

Toledo

MIS
Apr 9, 2002
5
US
We are attempting to eliminate the 2 remaining Novell servers here. Currently we are running Paradox 4.5 (DOS) on Novell. There is still over a year of life left to the 4.5 applications. I have the applications running under Win98 on the desktop and I have moved the network directories to a Win2K server with the same directory names and mappings as the Novell server. When I eliminate the Novell driver from the network neighborhood, Paradox gives the error:

Can't start Paradox: No directory specified for PDOXUSRS.NET.

I have added the -Net parameter to the command line but still get the same message.

I have altered the PARADOX.SOM file and tried choosing both Other and MS LAN Manager for the network types, but no luck. Still the same error.

By adding the Novell driver back into the Network Neighborhood, Paradox works without even logging onto a Novell server!

Any clues?

Thanx,
Bud Baumler
 
Are your drive letter mappings the same as they used to be under Novell? Paradox is a little sensitive to changes like that, so if you used to use P:\..., try using the same letters in the Win Network.
-DL
 
Yes, all drive letter mappings are identical to the original. Interstingly enough, I completely shut down the server Paradox used to run on yesterday and it continues to run. I still have one other Novell server on the network, but we are not attaching to it.

It seems as though Paradox needs to have the Novell client (and thereby IPX?) running to operate. This weekend I will shutdown the other Novell server and see what happens.

Thanx for responding.
 
It sounds like you might have several copies of Paradox executables -- which could make troubleshooting tricky. It's very possible to have paradox on the C: drive, but still accessing the network (which might explain your situation). See if you can hunt down all copies locally and on the network - make sure you control the 1 that is actually running this process, and go back to check the .som files, using OTHER as the network choice, and specify the .net directory.
-DL
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top