Hallo zusammen,
wegen eines moderneren Rechners muß ich eine Anwendung, die früher unter VMWare gelaufen ist, auf die Virtualbox migrieren.
Der neue Rechner ist eine AMD-Ryzen-Maschine, und die alte Anwendung stürzt wegen des Moduls NTVDM.EXE ab. Daher vermute ich, dass auf Ryzen-Maschinen wegen dieses Moduls VMWare nicht funktioniert (auf Intel I7 funktioniert's).
Darum wollte ich Virtualbox verwenden. Als Vorbereitung habe ich die unter der VMWare benutzte LMDK-Datei mit dem Virtualbox-Modul VBOXManage.exe aus diesem Format in VDI konvertiert.
Anschließend wurde Windows XP installiert.
Problem ist nun, wie kann ich die ehemalige LMDK-Datei, jetzt VDI-Datei, zusammen mit dem WIN-XP-File benutzen.
Wäre schön, wenn mir jemand helfen könnte - danke darum im Voraus.
Virtualbox - Windows XP - Anwendung früher unter VMWare
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox - Windows XP - Anwendung früher unter VMWare
Answering in English.
-------------
Can you quote the exact NTVDM error message?
NTVDM is the Windows subsystem for running old 16 bit Windows applications. This includes applications from the Windows 3.x era, and application installers well into the Windows 98 era.
NTVDM is no longer available by default in Windows 10, it has to be selected as an optional feature. Also, NTVDM has never been available on 64bit Windows, not even as an optional feature. However if you install 32bit Windows 10 then NTVDM is still available.
------------
There are several good reasons to prefer VDI over VMDK format, just as there are reasons for preferring Seagate v.s. Western Digital - however these are management questions for the host, it doesn't affect the content of the disk in any way, so inside an XP guest it makes no difference. Beyond that language issues become a problem, because I don't really understand what your question is here. The VBoxManage tool can be used to convert between VMDK and VDI, but that isn't actually necessary as VirtualBox can use both formats.
-------------
Can you quote the exact NTVDM error message?
NTVDM is the Windows subsystem for running old 16 bit Windows applications. This includes applications from the Windows 3.x era, and application installers well into the Windows 98 era.
NTVDM is no longer available by default in Windows 10, it has to be selected as an optional feature. Also, NTVDM has never been available on 64bit Windows, not even as an optional feature. However if you install 32bit Windows 10 then NTVDM is still available.
------------
There are several good reasons to prefer VDI over VMDK format, just as there are reasons for preferring Seagate v.s. Western Digital - however these are management questions for the host, it doesn't affect the content of the disk in any way, so inside an XP guest it makes no difference. Beyond that language issues become a problem, because I don't really understand what your question is here. The VBoxManage tool can be used to convert between VMDK and VDI, but that isn't actually necessary as VirtualBox can use both formats.