Hi,
i created an VHD-image of an old Pc, with installed WIN95. On this old machine (in WIN95) is still a DOS program running. So i set up a VM on my Host machine, just using the WIN95 option and included the VHD-image to run the old machine as guest on my Host.
So far no problem about this, just some graphic drivers which are not found...
Now if i want to start the old DOS program (well on the original machine it works without any proglems), there is an Error message:
Lattice RPG Subsystem for S/36 Environment Version 4.01
Copyright(c) Applied Math. Software, 1992
Invalid user (#ANYUSER) is specified in WSID.TBLUngültiges Verzeichnis (the last 2 words in english invalid directory)
So anyone a clue about this Problem?
Problem with DOS program, running on WIN95 Guest
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Problem with DOS program, running on WIN95 Guest
I assume the DOS program was known to have been running correctly before the old PC was imaged?
It doesn't smell like a VirtualBox problem. To me this error smells more like a licensing problem: hardware differences have been detected and hence the existing user license is invalidated. Or, it could simply be that a default profile is being selected based on a hardware signature of some kind, and that profile has never previously been initialized properly.
It doesn't smell like a VirtualBox problem. To me this error smells more like a licensing problem: hardware differences have been detected and hence the existing user license is invalidated. Or, it could simply be that a default profile is being selected based on a hardware signature of some kind, and that profile has never previously been initialized properly.
-
Martin
- Volunteer
- Posts: 2562
- Joined: 30. May 2007, 18:05
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP, Win7, Win10, Linux, OS/2
Re: Problem with DOS program, running on WIN95 Guest
The other possibility is that this program uses a DOS extender which doesn't work in a virtual environment like Vbox.