Dark Willow wrote: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...)
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!
using Atari since 1986. ・ http://wet.atari.org ・ http://milan.kovac.cc/atari/software/ ・ Atari Falcon030/CT63/SV ・ Atari STe ・ Atari Mega4/MegaFile30/SM124 ・ Amiga 1200/PPC ・ Amiga 500 ・ C64 ・ ZX Spectrum ・ RPi ・ MagiC! ・ MiNT 1.18 ・ OS X
calimero wrote: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 wrote:
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.
Dark Willow wrote: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)
My Stuff: FB/Falcon CT63 CTPCI ATI RTL8139 USB 512MB 30GB HDD CF HxC_SD/ TT030 68882 4+32MB 520MB Nova/ 520STFM 4MB Tos206 SCSI
Shared SCSI Bus:ScsiLink ethernet, 9GB HDD,SD-reader @ http://phsw.atari.org My Atari stuff that are no longer for sale due to them over 30 years old - click here for list
Dark Willow wrote: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
simonsunnyboy wrote: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.
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.
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!
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
using Atari since 1986. ・ http://wet.atari.org ・ http://milan.kovac.cc/atari/software/ ・ Atari Falcon030/CT63/SV ・ Atari STe ・ Atari Mega4/MegaFile30/SM124 ・ Amiga 1200/PPC ・ Amiga 500 ・ C64 ・ ZX Spectrum ・ RPi ・ MagiC! ・ MiNT 1.18 ・ OS X
******************************************
********* 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???
using Atari since 1986. ・ http://wet.atari.org ・ http://milan.kovac.cc/atari/software/ ・ Atari Falcon030/CT63/SV ・ Atari STe ・ Atari Mega4/MegaFile30/SM124 ・ Amiga 1200/PPC ・ Amiga 500 ・ C64 ・ ZX Spectrum ・ RPi ・ MagiC! ・ MiNT 1.18 ・ OS X
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.
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)?