I have a couple problems using Amiga BASIC.

One problem is, when you save a basic program to a floppy.  in the file's Info.. it says the deafult tool is :AmigaBASIC.     the problem there is if you double click on the icon for the program in the floppiy's window, it seems to try to find AmigaBASIC on the floppy... in my case it's on the hard drive in SYS:
So is there a way to solve this?  What I've been doing is changing the info so that the default tool is SYS:AmigaBASIC...

Another seems to be the opposite problem... once the program is loaded into AmigaBASIC, if the program tries to open a file by just giving a file name, for example ...OPEN "foo.txt" FOR INPUT AS #1...   it can't find foo.txt, even though it resides on the floppy that the program was loaded from. I can fix that by specifying the floppy drive as "DF0:foo.txt"   but I'd like to make my program more generic than that since I can't predict which floppy drive, or hard drive a user will use to load my program.

It seems both problems are related to what the drive defaults are...

I've used DiskMonTools to repair FFS partitions over 4GB. It takes ages. For under 4GB I use the old Haynie classic DiskSalv!

Does it really? I own both 3.1.4 and 3.2, but will they be ok repairing a FFS of 3.9?

It might do 🤷🏻‍♂️ Might be worth updating the FFS first to 3.2.2. But as I have mentioned before. Backup the partition first before you try it.

Failing that. Backup the partition data by using Dopus or copy command to another media. Then perhaps try HDToolBox and reseting the partition and re-formatting. Then copy back the data.

I prefer to use PFS3AIO to FFS as it’s quicker and there are plenty of fix tools out there for it.

Hi,

Tried everything, read everything I could find online.
Amiga OS version 3.2.2.1 with a Raspberry Pi 3A+ on a A1200
I also upgraded P96 V2.0 from aminet to P96 V3.4.1 from Icomp.

I am using Emu68 1.0.1 (25.03.2024). git:98b83c7
On the screen connected via HDMI, a fine picture appears with "68 PISTORM"

But when I press "Emu68-VC4" under Storage -> Monitors the following error appears.

Software Failure
Emu68-VC4
Program failed (error #80000008).
Wait for disk activity to finisk.

Have checked whether there was anything strange via SnoopDos, but here everything is OK until the above error appears.

Hope someone can show me how to solve this problem.
Just an extra bit of info, wifipi works with wap2 without problems.

Solved
I went back and forth until I got to Emu68-tools-20240421-a8ca6b.zip
Here #80000008 disappeared and I now have a picture via HDMI

Hi. I recently got my old A1000 back from my friend. This machine was given to me nearly 20 years ago. I have honestly only turned it on once, when i was given it, and i vaguely recal there being an issue of some kind. it pretty much got used as a monitor stand for about 6 years before ending up in the loft until i gave it away about 3 years ago. My friend did nothing with it either and returned it.

It's time to get the old girl working so i pulled it apart and tested the PSU first. Under 1amp load on the 5v rail, all voltages look good and stable and i got a good stable tick. connecting the board brings up the the Kickstart logo, albeit in magenta. something had gone out of spec, but is back now, and it's starting up in the correct colours and the drive is ticking fine. However, when it loads kickstart and resets, it sticks on a white screen. swapping the CIAs, didnt work, it wouldnt startup at all.

I fitted a PiStorm with a plain install, just mapping KS1.3, and again, with the CIA's in the original position, i just get a white screen. Swapping the CIA's iget further, to the 1.3 boot screen, however the floppy doesnt work.

I got it to boot Caffeine but it reports the drive as bad and the mouse doesnt work (well, at least the right button does. I dont have a keyboard to test.

I figure i have at least one faulty CIA. can I replace these with A500 CIA's or are there limitations on the versions it will take?