> I've found a drvspace.bin in c:\windows\command but it doesn't get
> loaded and, using selective loading, I can't find any combination of
> things which I can take out which don't either a) do nothing or b)
> prevent the system from loading.
If it doesn't work from true DOS prompt,ie pressing F8 when
"starting windows" first appears then choosing "command Promt only"
&CD'ing to the directory to run HELI10.EXE i think you can pretty much
forget anything windows might be doing.
But the autoexec has already run,so any TSR's etc could have an impact.
I know when i had a Matrox Mystique it used to crash when i experimented
with SETVBE (part of Matrox's software to extend VESA capabilities).No
error codes though just crashed the machine & put shit on the screen
whenever i tried to run HELI10 from DOS or Windows.
> Thanks Martin but I already have 4 different versions of V10 including
> a pre-release and one Wendy sent me quite recently. They behave
> slightly differently but none of them work. I have got as far as
> getting error 208 consistently with both Aero10 and Heli10 but that's
> the best I've managed.
I thought you probably would have all the versions
> I think I'll try uninstalling my LAN s/w, which is all I've added
> recently, and see if that does anything.
Sounds likely,if that's the only thing that's changed and it was working
then it could be the problem,you can but try.
It would help to know what these error codes 208 etc means ,i would
think.Is that generated by the CSM software rather than the OS?