CompuServe Messages

Hello Yann, Well, after all that! <g> Good luck, cuz you'll need it! Just teasing (sort of). But definitely drop me a line if you need a hand. I can't promise miricles (or spelling), but we all should be able to chip in something. As for running Targa+, it should be a snap. In the preferences for 3DS in OS/2 (right-click on the 3DS icon, then click on the arrow next to OPEN. Choose SETTINGS), there is a section called SESSION. Click on that leaf, which will open that page in the notebook (pretty fancy, huh). In there you'll see a button called DOS_SETTINGS. Click that and you'll find a whole list of configurable settings for each dos session. For the 3DS one, you would have it load the Targa+ device drivers, using the DOS_DEVICE line. Hilite that and you'lll see a window on the right that is empty. Simply type in there the targa+ DEVICE= commands, just as you would in the dos CONFIG.SYS file. Consider this space each sessions own personal CONFIG file. Once those are in, click on SAVE at the bottom of the main SESSION window. Then click in the top lefthand corner of the remaining SETTINGS window. I'm not sure if I'm talking down to you here. I think you'll find once you find one thing, it'll all fall into place down the line (OOP!). Anyway, the next step is to load up the AUTOEXEC.BAT file with your SET RADPDI= (? I can't remember it's been a while since I used this!) – whatever the command… Now each DOS SESSION can run it's own AUTOEXEC.BAT. You could simply place the SET call in the general AUTOEXEC in the root dir, but then every DOS session that uses that BAT file will SET RDPADI, and visa versa. Anyway, simply create or edit the AUTOEXEC.BAT file, using the OS/2 SYSTEM EDITOR in the PRODUCTIVITY FOLDER. Place the customized 3DS AUTOEXEC in the 3DS subdir. Go back into the settings of 3DS (right click on the icon, etc). You'll see another line that reads DOS_AUTOEXEC. Hilite that and you have a space to type the full path to this new AUTOEXEC.BAT file. When you launch 3ds, you will now get the DEVICE drivers (hopefully) and the AUTOEXEC.BAT will launch with it. And remember, every program can be run like this – in it's own virtual machine, with it's own settings. Well, are you sorry you asked? <g> James