Easymint installation

[wongck]

Yes, As Christos mentioned, if without a video= line, it will default to what ever the video mode is currently in.

Assuming that it is the rez that when wrong....

For your case, now on a TV, you may want to force it to TT med rez mode, which I think can be output on a TV.
( IIRC, I tested that mode on the TV with my 1st Falcon that I got 2nd hand in US ).
So just put video = 6
Also remove any include files as you do not want it to change your settings.

Good luck.

[christos]

You don't need to do anything like that. If video =27 for example, it will boot at 640x480x256 on PAL. I don't change my settings when i connect it to RGB.

[wongck]

You don't need to do anything like that. If video =27 for example, it will boot at 640x480x256 on PAL. I don't change my settings when i connect it to RGB.

Ok, so you are saying that it is most likely not a video setting issue.

The next thing to check is the xaaes.log file inside the xaaes folder.
Boot to TOS to do this. Look for any errors that it may report.

You may also want MINT to make a log file. The Mint.cnf file should have some explanation on how to do this.

[christos]

I have a feeling that it may be a problem with loading images and/or widgets. Try to turn these things off.

[paul92706]

You don't have a line that reads video=<some value>?? It should be the first real line in xaaxes.cnf.

There is no video line in Xaaes.cnf. But as christos mentioned it should boot to default video mode.

[paul92706]

[Latz] The screen cycles to fast even with step by step enabled to catch the last 2-3 messages, it quickly drops into white screen.The only message i caught with my eyes were "Loading Kernals" and some file /path names i couldnt write down.

[paul92706]

You don't need to do anything like that. If video =27 for example, it will boot at 640x480x256 on PAL. I don't change my settings when i connect it to RGB.

Ok, so you are saying that it is most likely not a video setting issue.

The next thing to check is the xaaes.log file inside the xaaes folder.
Boot to TOS to do this. Look for any errors that it may report.

You may also want MINT to make a log file. The Mint.cnf file should have some explanation on how to do this.

I will check the .log file in hopes i can catch something.

[paul92706]

I have a feeling that it may be a problem with loading images and/or widgets. Try to turn these things off.

This is where i think the problem resides, now how do i go about disabeling images/widgets? thanks

[paul92706]

[wongck] i tried adding that line video=6 but no success i think its not video related. hmmmm its got me wondering.I just checked my Xaaes.log it seema like everything executed properly but i noticed it could not determine NVDI version and my deffault screen mode is 1.

[Latz]

Hmm,
perhaps you can post xa_boot.log and your xaaes.cnf here, so we can have a look.
Are you sure that xaaes starts?
Latz

[Dal]

You have used DirSort to ensure NVDI runs before Mint?

Mint should always be the last program to start in the Auto directory

[paul92706]

If there is no video line xaaes will run on the resolution that the system is currently on. So if you boot in STHigh XaAES will run in ST high.

ya i should be getting display in ST High mode through my TV. i asume its something else.

[paul92706]

You have used DirSort to ensure NVDI runs before Mint?

Mint should always be the last program to start in the Auto directory

Hi dal i dont even have NVDI installed, isn't that just for fonts and printers? is it recommended to install NVDI?

[Dal]

I was just going by this line in your post..

I just checked my Xaaes.log it seema like everything executed properly but i noticed it could not determine NVDI version

It read as if you were surprised it couldn't determine the NVDI version. As you don't have it, then this would behaviour would be expected

[paul92706]

I was just going by this line in your post..

I just checked my Xaaes.log it seema like everything executed properly but i noticed it could not determine NVDI version

It read as if you were surprised it couldn't determine the NVDI version. As you don't have it, then this would behaviour would be expected

Im gonna install NVDI and if all else fails i will display my Xaaes.log and Xaaes.cnf

[jfl]

Hi dal i dont even have NVDI installed, isn't that just for fonts and printers? is it recommended to install NVDI?

NVDI replaces both the VDI (hence it's name) and GDOS (fonts and printers). The VDI part will make anything drawn to the screen much much much faster (anything drawn via the VDI, obviously). The original VDI is dog slow.

[paul92706]

Ahhhhh! At last i finally got Mint installed! it was for the fact i didnot have NVDI installed! i guess i will blame myself as i didnt fully do my homework on installing this OS. thanks guys for your help n support! ur truely pros at this! so i say

[wongck]

I have a feeling that it may be a problem with loading images and/or widgets. Try to turn these things off.

if you're taking about the Hires widgets, then find the folder IMG and rename that (like to XIMG) so that xaaes cannot find the widgets to load.

[wongck]

[Latz] The screen cycles to fast even with step by step enabled to catch the last 2-3 messages, it quickly drops into white screen.The only message i caught with my eyes were "Loading Kernals" and some file /path names i couldnt write down.

yeap... it dropped into xaaes kernal.
So you need to look into what happens next in the xaaes log file.

[wongck]

Hi dal i dont even have NVDI installed, isn't that just for fonts and printers? is it recommended to install NVDI?

NVDI replaces both the VDI (hence it's name) and GDOS (fonts and printers). The VDI part will make anything drawn to the screen much much much faster (anything drawn via the VDI, obviously). The original VDI is dog slow.

IIRC there was some mention either here or at dhs.nu that NVDI is needed for Mint to run correctly.
I can't remember.... getting old.... is that, that it applies to CT6x system only or to all system in general.
But I don't think it is needed as I am sure I had run Mint without NVDI... but i had it on almost always because I don't like a slow dog
( with CTPCI/ATI I don't think it is needed because Didier had fvdi stuff in it.).

.... someone please confirm this.

[DarkLord]

Its absolutely required here, on my Falcon 060. It won't boot up correctly
without it.

Wong, wasn't it something to do with the blitter?

[jfl]

Its absolutely required here, on my Falcon 060. It won't boot up correctly
without it.

Wong, wasn't it something to do with the blitter?

NVDI is of course not require to run MiNT (that would be outragous, since NVDI is closed source) but NVDI disables the blitter (the blitter causes problems with the CT60/3).

[wongck]

So it's a CT6x thingy.

[Klapauzius]

NVDI is of course not require to run MiNT (that would be outragous, since NVDI is closed source) but NVDI disables the blitter (the blitter causes problems with the CT60/3).

I'm just a Mint newbie, but I haven't got FreeMint 1.17 working on my Falcon030 without loading NVDI before Mint. I'm sure it can be made to work without NVDI, I just didn't manage to do so.

[wongck]

Found this post from joska.

XaAES works fine without NVDI. But if you have a CT60 you *need* NVDI (or fVDI) because TOS VDI doesn't work without a blitter, and the blitter doesn't work on a CT60 in 060 mode.

And in the post above it, I managed to run Mint without NVDI in videl, not CTPCI.
It seems to have mixed results....