Trident won't run after Deneb / Poseidon install

[mbrantley]

I'm still stuck at getting my USB to LAN working with my Deneb on the 4000 (see http://www.amiga.org/forums/showthread.php?t=36885 ) so I decided to put that aside for a bit and work on something else.

Namely, installing my second Deneb card on my newly souped-up 2000. (Purchased GVP 040 board, MegaChip, Video Toaster and Personal Animation Recorder from a.org members for it, Deneb from Amigakit and some newly made GVP SIMMS from Software Hut.)

I had to set both the Rescue and Test jumbers on the Deneb to get the DenebInstall virtual partiton to show up. Did that, installed the stuff and then removed the jumpers and rebooted.

Only hitch now is that the Trident program in Prefs won't run. Gives an error message of not being able to open a screen (though I know from my 4000 Deneb install that the program opens a Workbench window and not a screen of its own).

Any ideas? I wonder if I should keep that Test jumper installed for any strange reason...

[sandpiper]

Could be an MUI problem? Did you copy your MUI prefs from your A4000? There may have been Trident MUI screen prefs settings in Env:mui looking for a specific screen. Just an idea.

[Darrin]

mbrantley wrote:

Only hitch now is that the Trident program in Prefs won't run. Gives an error message of not being able to open a screen (though I know from my 4000 Deneb install that the program opens a Workbench window and not a screen of its own).

Any ideas? I wonder if I should keep that Test jumper installed for any strange reason...

I had that message a couple of days ago when reinstalling OS3.1 as my OS3.9 installation wouldn't work with my Fast ATA4000 card installed (pointer wouldn't move, while everything else seemed to be running fine in the background).

When I got the "Unable to open window!" error it was after installing the Deneb software then MUI.  I wiped the drive and then reinstalled OS3.1, installed MUI and then installed the Deneb software and everything worked.  Of course, this may be totally unreleated as to when it worked or didn't work.

Right now have OS3.1 running fine with the CV643D, Deneb and Fast ATA4000 with 2 hard drives on the Fast ATA and a DVD+RW attached via the Deneb.

The only annoying problem is that with the Fast ATA4000 attached booting takes forever either from the hard drive or floppy.  There's a long pause after power up before the floppy is checked and then another huge pause before the hard drives are checked.  From power up to loading Workbench takes a whopping 1 min 55 secs!

[mbrantley]

OK, so to be sure I reinstalled MUI (nothing had been copied from 4000), put the jumpers back on the Deneb and reinstalled the Deneb stuff. Now when trying to launch Trident I get a "Failed to create application" error.

[platon42]

If the Trident window won't fit on the screen and MUI doesn't manage to reduce the fonts further, Trident will fail to open the window. A screen of 640x256 is not enough I'm afraid. You could try temporarily setting the size of the workbench screen to a bigger dimensions (autoscroll) and try again.

[mbrantley]

That's got to be it then. This is your basic, old-fashioned, native, nonflickering 640 x 200 Workbench screen. I will go change resolution...

[mbrantley]

Presto! That worked, Chris, as you knew it would.

Thanks, all.

Now back to my previously interrupted problem, of getting my Belkin (usbpegasus.device) network adators working with my Denebs...

[Darrin]

platon42 wrote:
If the Trident window won't fit on the screen and MUI doesn't manage to reduce the fonts further, Trident will fail to open the window. A screen of 640x256 is not enough I'm afraid. You could try temporarily setting the size of the workbench screen to a bigger dimensions (autoscroll) and try again.

Ah, that explains my problem too then.  I usually set Workbench non-RTG screens to High Res-Interlaced, but during my initial reinstallation I was using a lower resolution screen.  Duh!!!   :-)