Where to start with Mint?

[Eero Tamminen]

This is weird. When I fired up the system today, it came to the GEM desktop as usual. When I went to launch xaloader.prg it wouldn't run. All PRG files seemed to be being shown as non-executable files (the sheaf of papers instead of the usual PRG icon). When double clicking on them, the prompt about whether or not to display the file came up.

Disable GSXB Mixer. It's 68k asm code and apparently not "emulated" well enough by FireTOS, so it messes things up.

(That issue was found out by Frank Wille, when porting VBCC to Firebee which was loaned to him for that porting. Frank's a long time Amiga/NetBSD guy who's never used a real Atari, so it was nice of him to work on that port, but he's had quite a lot of weird problems like that with his Firebee setup...)

[Dark Willow]

Would this still apply to 68030 with TOS 3.06?

[joska]

He has a TT, not a Firebee.

[Dark Willow]

He has a TT, not a Firebee.

She

[calimero]

how mint.prg know where to look for mint folder? e.g.:

does mint.prg version 1.18 is hardcoded to look for C:\mint\1-18-0\

and mint.prg version 1.17 is hardcoded to look for C:\mint\1-17-0\

???
i can't find any configuration file for this so I assume it is hardcoded?

[joska]

Correct, it's hardcoded.

[calimero]

I have problem, but not sure where to dig for answer:

I associate *.jpg file to zview.app - if zview is not started, double click on jpg file will start zview and open image
but if zview is already in memory, and I double click jpg file - nothing happen!

I try to change configuration regarding AV protocol in Jinnee but it is same.
I also try TeraDesk but problem is same!

[Dark Willow]

Are the filenames displayed in lower case?

Oh, sorry missed this. Yes. It's in lowercase.

[OL]

I have problem, but not sure where to dig for answer:

I associate *.jpg file to zview.app - if zview is not started, double click on jpg file will start zview and open image
but if zview is already in memory, and I double click jpg file - nothing happen!

I try to change configuration regarding AV protocol in Jinnee but it is same.
I also try TeraDesk but problem is same!

Look at my answer it should help you:

http://www.atari-forum.com/viewtopic.ph ... 12#p232412

Olivier

[Dark Willow]

Are the filenames displayed in lower case?

Oh, sorry missed this. Yes. It's in lowercase.

Just a bump on this - does anyone have any ideas about this one?

[helmut]

Just a bump on this - does anyone have any ideas about this one?

I've seen it too, long ago, I don't remember what to do. I avoid using the TOS-desktop whenever possible. Maybe it runs under MiNT-domain, which would be a bug in MiNT - don't know.

In case you want to run XaAES you should set xaloader as auto-run in newdesk.inf (hope it has no lower-case then)

What filesystem is it? On ext-2 or VFAT it might be possible to get lowercase, not on FAT. You might also have lowercase on FAT, which could be caused by some copy-programs. You can try to delete the lowercase-files and copy again with correct case in this case.

-Helmut

[wongck]

Just a bump on this - does anyone have any ideas about this one?

This is happening before you launch xaloader?
Even on the TOS desktop ?

Try to rename your desktop.inf to desktop.inx and reboot (i.e. just like no desktop,inf defined).
See if it helps.
(of course all your setting will be gone, and you need to setup you apps association again)

[mfro]

Do you have FS_VFAT enabled for your boot drive in MINT.CNF? This would be a bad idea.

[Spacedcowboy]

Yes please, especially if you have the simple, plain setup! -

VanillaMiNT???

I liked that name Go to http://atari.nvg.org/VanillaMiNT/ to download the first version. Tested briefly on my Falcon030, but should work on a TT too.

Amazing work, honestly i think the Atari community missed a distribution set like this for 20 years.

Hmm. Since I wrote something similar (admittedly a bit more unix-focused, but it worked well with the Gem desktop too) *over* 20 years ago, back in 1992, funnily enough called the "mint distribution kit", I'm not sure that's the case...

See http://www.umich.edu/~archive/atari/Min ... b_kit/Doc/ for details. As I recall, I only had an STe at the time, and I got scattered reports of it not working on the TT, but I couldn't really test it on anything 030, so ymmv if you tried it out now (I wouldn't bother, I'd use the above, much more up to date ). I'm pretty sure that was GFA basic's fault anyway

Simon.

[simonsunnyboy]

Is there any progress on VanillaMiNT? Such as kernel updates or so? I hope the project will not fade away.

[joska]

Is there any progress on VanillaMiNT? Such as kernel updates or so? I hope the project will not fade away.

Due to changes in my personal life I have very, very little time and energy for my hobbies. So VanillaMiNT (and all other Atari-related projects) has been put on hold. Anyway, there isn't much to update in VanillaMiNT. I attempted to update it to 1.18 but faced several problems and gave up. Maybe 1.18-cur is better suited for plain Falcons.

[simonsunnyboy]

Lukas Frank over at atari-home tried to replace the VanillaMiNT components and it seems a minimum system for 68000 cpus would be a possibility as well.

[frank.lukas]

Quick and Dirty tested under Hatari with MiNT 68000 Kernel 1.19 on a 4MB ST Machine …

http://forum.atari-home.de/index.php?to ... 9#msg83009

The netconf.prg is not runing, maybe it is for a 030 CPU !?!

[joska]

Netconf.prg is compiled for ColdFire/68020-60.

[mdivancic]

Working my way through the install of MiNT. Got root.tar installed as suggested here, but tcsh is lacking some.

Anyone have a good .cshrc file for tsch?

[calimero]

ok, this start to being very annoying... I had 1.17.0 with NetUSBBee and everything works fine than I change two things at once - replace NetUSbee with SvethLANa and 1.17.0 with 1.18.0.

I activated SvethLANA by: ifconfig en0 addr 192.168.100.30 netmask 255.255.255.0 up
I am pretty sure that SvethLANa works fine since I can ping local address and get response. What I can not setup is routing!

my default routing table looks like this:

Code: Select all

Destination        Gateway    Flags       Ref      Use   Metric    Iface
192.168.100.30     *          UH          1        6     0         lo0
127.0.0.0          *          U           1        0     0         lo0
127.0.0.0          *          UH          1        22    0         lo0

than I add route: route add default en0 gw 192.168.100.1
and I get new line in routing table:

Code: Select all

Destination        Gateway          Flags       Ref      Use   Metric    Iface
default            192.168.100.1    UGD         1        0     0         en0

and at this point even ping 192.168.100.30 stop working! (it works if I let him for about 5 minutes: only than it start to response)

is something wrong with my routing configuration?

[calimero]

ok, I just return NetUSBee to ROM port and add it:

ifconfig ne0 addr 192.168.100.31 netmask 255.255.255.0 up
route add default ne0 gw 192.168.100.1

and I can ping my router at 192.168.100.1 but when I plug cable in SvethLANa I can not ping it!

so problem is in SvethLANa or driver or... ?!? Lights on svethlana response on insertion of cable (both lights turn on) but it does not blink on PING! (NetUSBee orange light flash while ping is in progress!)

if driver is defect, will svethlana appears in ifconfig -a ?
driver is 36.283 bytes... svethlan.xif

[calimero]

I just try to post BOOT.LOG from MiNT but NetSurf crashed so I will retype it on Mac.

So in BOOT.LOG I have this part:

Code: Select all

******************************************
*********    SVEthLANa driver     **********
******************************************
002043587839
SVEthLANa driver v0.1 |en0|

svetlana_open 0x10E70DD$
...
...
...
svethlana_services 0x10E71AE4
[/coda]
next is driver from AssemSoft for NetUSBee...

so I suppose that driver is also ok?
I use same ethernet cable for Svethlana and NetUSBee...

maybe ribon cable from SuperVidel to Svethlana is damaged???

[Ato]

Code: Select all

Destination        Gateway    Flags       Ref      Use   Metric    Iface
192.168.100.30     *          UH          1        6     0         lo0
127.0.0.0          *          U           1        0     0         lo0
127.0.0.0          *          UH          1        22    0         lo0

Code: Select all

Destination        Gateway          Flags       Ref      Use   Metric    Iface
default            192.168.100.1    UGD         1        0     0         en0

The first table shows 192.168.100.30 being assigned to lo0 (virtual loopback interface), the second table shows the physical en0 interface. Something went wrong when you set up the physical interface with ifconfig. When configuring the interface, check the return value of ifconfig. If != 0, the value (man ifconfig) should tell you what went wrong.

Cheers,
T.

[MacFalcon]

I have the same issue here with my svethlana... But I have never had it running... Installed it with easymint... dhcp doesnt´t work, is listening forever... and manual config doesn´t work, too. I cannot ping anything... svethlana is blinking orange when trying to ping. Double checked the (damn) ribbon cable...

Any ideas... Should I go back to older mint version (1.16)?