> Yes, only there, which can be easily solved doing a couple of "pop bx"
> instead of the "pop gs" and "pop fs". The only other 386 specific code
> is in the VMWARE interface.
"push gs" and "push fs" are issued by the keyword "interrupt" and
compiling with 386 optimization.
compiling without 386
Hi Bernd,
2011/10/9 Bernd Blaauw :
> By the way, I'm able to load VMSMOUNT (0.3) twice somehow, by having it
> loaded at top of autoexec.bat, then other drivers, then running VMSMOUNT
> again at commandline.
The installation check in VMSMOUNT is very rudimentary (similar to
MSCDEX) and it seems t
Hi Tom,
2011/10/10 Tom Ehlert :
> "push gs" and "push fs" are issued by the keyword "interrupt" and
> compiling with 386 optimization.
Without 386 optimization, "interrupt" generates similar code, but
"push gs" and "push fs" are changed by dummy pushes ("push ax", IIRC)
so everything else is in t
At 01:38 PM 10/9/2011, Eduardo Casino wrote:
>Would you be so kind of testing it in one of your 286? It should fail
>with "ERROR: Not running on top of VMWARE."
>
>http://sourceforge.net/projects/vmsmount/files/Test/
Will do. Unfortunately, the best machine to test it on, an IBM PS/2
Model 50Z is
