Author: jeff (oh-lyndhurst2a-114.clvhoh.adelphia.net)
Date: 12-15-2001 17:35
I was using this, as FMH would probably know. I'm not sure why it won't start with just 1024x768.PRG in the auto folder. That's strange.
But as a rule, once you do get it to boot wiht only 1024x768 in the auto folder, you should not run NVDI straight out of the package. If I remember correctly from using SpeeodGDOS and other software, the order in which things are run are important.
NVDI should be run first in the auto folder. Absolutely. This is how I had SpeedoGDOS set up with my AlberTT. But, you should delete all the NVDI screen drivers. These cannot be run since NVDI does not have a driver for the AlberTT. That way, NVDI will provide the font, printing, and enhanced VDI routines, but will not attempt any direct hardware tricks since they won't work with the ALberTT.
After NVDI, run the AlberTT driver. After that iot shouldn't matter what's run. if you have it in the other order, you end up with a 640x480 desktop crammed in the top corner of you 1024x768 screen. This is because NVDI will not recognize the AlberTT. The ALberTT fools the TT into thinking it is in TT-Medium resolution so programs can't get confused. This works fine except when font handlers like NVDI try to operate.
SO just two things:
1. Start NVDI first WITHOUT screen drivers (important!)
2. Start 1024x768.PRG second in the auto folder.
Then see if that works. There shouldn't be any hardware settings to change. the AlberTT driver nis quite moody, so you just have to keep trying to get it running. If it doesn't work, I suggest buying a Galaxy from Mario Becroft. That's what replaced my AlberTT!
jeff
|
