04-22-2005, 04:51 AM
Hmn. So there are two things possible now. If SBM Productions is running an NT version of windows with a NTVDM that behaves strange when executing shell commands while in vesa (like mine), I can recommend the DIR$ routine using the stardard &H21 dos interrupt.
If this is not the case and the windows if fully compatible with dos (9x), the simpler method of using shell can be used (however, this then won't work on the NT windows versions with obviously weird ntvdm).
Now for the replies...
@ Mac: no file at all was created. I know for sure the executed shell command is valid. Shell just terminated vesa and quit the program. Or sometimes it even crashes.
@ Antoni: I experienced something similar too. Was trying out uGL and one second a program worked, the next second it crashed. WinAmp was playing another song the second time. Also it seemed to conflict with drivers sometimes, making me lose my videodrivers, strangely.
If this is not the case and the windows if fully compatible with dos (9x), the simpler method of using shell can be used (however, this then won't work on the NT windows versions with obviously weird ntvdm).
Now for the replies...
@ Mac: no file at all was created. I know for sure the executed shell command is valid. Shell just terminated vesa and quit the program. Or sometimes it even crashes.
@ Antoni: I experienced something similar too. Was trying out uGL and one second a program worked, the next second it crashed. WinAmp was playing another song the second time. Also it seemed to conflict with drivers sometimes, making me lose my videodrivers, strangely.