Amiga Logo (Turtle programing language) not running on OS 3.2

[thyslo]

Im always a bit curious about old, obscure programming languages and so I gave AmigaLogo a try. This is a language for turtle graphics and, if I'm not wrong here, its Amiga port was done by RC Mical in 1989.

So I took the ADF from archive.org and copied the Logo directory from there to my Amiga hard disk. (Amiga OS 3.2.1 installed there).

Now, when clicking one of the provided demos at least they start, so AmigaLogo *seems* to work. But all text that is printed looks faulty..as if there'd be something wrong with the used font.

Maybe anybody here played with Logo and has an idea how to fix problem?

[Snoopy1234]

I've recently bought Logo for my Apple II Plus. Just for the memories of when the teachers were really unsure about computers at school when Logo came out and were not trusted
Back to your quest, I know Amiga Basic has a 020 patch for A1200's otherwise the libraries don't let it work, so the same might be true for Logo. There may be a patch needed if you're running 020+ CPU..

[thyslo]

Yeah this could be the case. But I was hoping that it would be compatible to new Os's because its developed by the inventor of Intuition.

[Nor Bert]

Run LOGO from the floppy disk and write if everything is ok. If it still does and you want to run LOGO properly you can use WHDLOAD Generic.

kick3.2 is the problem

[Snoopy1234]

I'd try deleting the files in Logo/libs that are already in your SYS:Libs folder and check the rest if they are compatible with your system.

[davideo]

Originally Posted by thyslo

Now, when clicking one of the provided demos at least they start, so AmigaLogo *seems* to work. But all text that is printed looks faulty..as if there'd be something wrong with the used font.

Maybe anybody here played with Logo and has an idea how to fix problem?

Which text seems faulty?

It seems to work here on 3.2.1

[thyslo]

Originally Posted by Snoopy1234

I'd try deleting the files in Logo/libs that are already in your SYS:Libs folder and check the rest if they are compatible with your system.

I have already done this indirectly by copying only the Logo directory from the floppy disk to hard disk. So it uses only the 3.2 libs instead the 1.3 ones which are on the disk.

[thyslo]

Originally Posted by davideo

Which text seems faulty?

It seems to work here on 3.2.1

This is good to hear. So I'll verify it after work and maybe post a screenshot.

[Snoopy1234]

Originally Posted by thyslo

I have already done this indirectly by copying only the Logo directory from the floppy disk to hard disk. So it uses only the 3.2 libs instead the 1.3 ones which are on the disk.

If so; does the 3.2.1 libs account for all on the Logo disk libs? What about translator.library, would you have to add any (updated) to SYS:Libs? or maybe some are renamed and in rom now?

[thyslo]

The SYS:Libs directory on my 3.2 Harddisk contains a translator.library, the release 42.4 from 1995. And it works well with the updated *Say*, which was written but never released for WB2.0.

[thyslo]

I've attached a screenshot of the faulty screen which appears when I run the *Intro* demo of Logo on my 3.2 installed harddisk.

The error also occurs when I start the Amiga without startup-sequence and run Logo directly from CLI.

Then I checked the Logo ADF with WinUAE and booted it it with some configs:

- A500 / 1.3 ROM: Workbench was loaded, Logo runs great and without that faulty screen

- A1200 / 3.1 ROM: Workbench was loaded, Logo runs great and without that faulty screen

- A1200 / 3.2 ROM: Workbench was not loaded due to missing icon.library and got stuck in boot CLI. (I suppose also the workbench.library is needed on disk for 3.2). Couldn't test Logo.

So when I have some time, I will take a close look. There is certainly a solution to this problem.

[Galahad/FLT]

I would use snoopdos to see what files its looking for, chances are you have a locale file on the hard drive its loading up which is messing with the text, if it cant find said file, it just continues normally

[thyslo]

I've already checked with SnoopDos. Strangely the only thing it reported as missing / failed to load was the cybergfx.library.

This is strange because I don't have anything cybergraphics related installed on that system. Picasso96 is installed, but this is not cybergraphics.

[thomas]

Originally Posted by thyslo

Strangely the only thing it reported as missing / failed to load was the cybergfx.library.

This is strange because I don't have anything cybergraphics related installed on that system.

Why is it strange that cgx cannot be opened if it is not installed? The only way to detect whether something is installed is to try to open it.

Picasso96 is installed, but this is not cybergraphics.

That's what is really strange and probably the cause of your gfx corruption. P96 should contain an emulation layer for CGX so that CGX-aware programs also run on P96.

As Logo tries to open the CGX lib apparently is is aware of RTG graphics. But it fails to detect it because the lib fails to open. So Logo runs with the native chipset in mind although you have RTG software installed.

You should make sure that P96 is installed completely, including the CGX emulation layer.

Or disable P96 altgether when you run Logo.

[thyslo]

I find it strange because Logo is from 1988 or 89. I'm not 100% sure but believe that P96 and CGX were not available at that time.

Thanks for your hints with the CGX emulation layer and disabling P96 (which on my A1200 just was installed to use the Native driver) for a try.

[davideo]

I don't think it's a fault with 3.2.1 because it loads and displays fine under WinUAE and on my real 4000D with 3.2.1

This screen shot is from WinUAE but I get the same on my 4000D (with a PIV)

[Snoopy1234]

I've had apps not running properly or at all looking for cybergraphics.library when CGX 4 isn't installed. I had to wait until a cd came up on ebay as it's under licence. Fixed the issue though.

[thyslo]

Originally Posted by davideo

I don't think it's a fault with 3.2.1 because it loads and displays fine under WinUAE and on my real 4000D with 3.2.1

This screen shot is from WinUAE but I get the same on my 4000D (with a PIV)

Thanks for the confirmation that it does indeed work on 3.2. So I can investigate and check my Amiga configuration until it works for me too:-)

@davideo Could you possibly have a look with SnoopDos, if it also tries to open the cybergraphics.library and this fails?

[davideo]

Here you go

[thyslo]

Thank you