Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

For awhile now, one of my clients has been stuck with Corel Paradox 4.0 (it used to be the biggest database system in the DOS days, until Microsoft released Access in the early 90's) so for awhile I've managed to keep it on life support on Windows XP for a few years, however since switching to Windows 7 x64, I've had to resort to using XP Mode as the sandbox to keep it up and running.

While I am able to run Paradox as usual in XP Mode, I'm having a serious issue where if I try connecting the install to the network share (which is located on the Windows 7 portion of the system), Paradox keeps exiting because it says the serial number is invalid.

Now, I know for a fact that this is an issue with the virtual loopback adapter and also having the VM linked to the physical ethernet adapter -- and while I have solved this issue before, most of my fixes have been bandages since after a few weeks the issue pops up again.

Long story short, I wanted to ask if there is a permanent way to link a DOS program to a network share address. For example, when I try doing \tsclient\paradox (the Windows 7 Address) I keep getting an error saying I need a valid network address.

I've tried mapping that folder to various drive letters such as P:\Paradox -- but for some reason that keeps failing over time.

For what it's worth, Paradox uses a .SOM file to store the network settings, however it isn't editable in Notepad but rather it's controlled by a wizard in Paradox. But if that extension rings any bells, I'd welcome any insights.

share|improve this question
    
> ...Corel Paradox 4.0 (it used to be the biggest database system in the DOS days, until Microsoft released Access in the early 90's) And Lotus 1-2-3 used to be the biggest spreadsheet program in the DOS days, until Microsoft released Excel in the mid 80's. :-| –  Synetech Jun 12 '12 at 15:39

1 Answer 1

up vote 0 down vote accepted

Although I doubt anyone else will be in the position I was with my prior client I just wanted to quickly post the solution to the issue. What we simply did was buy a refurb machine with Windows XP and installed Paradox DOS on there and it worked flawlessly again.

Not exactly the most ideal solution, but when it comes to legacy systems - obviously standard rules go out the window and you just have to do what works.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.