I've had a Catweasel MK4 for some time and figured it was time to put it to good use.

I put it in a PCI slot on my x5000, found that catweasel.device was already in the DEVS: directory. I got a straight through floppy cable and hooked up the drive which shows up as drive 1.

I set my prefs in the Catweasel setup under PREFS to Drive 1, PC HD drive and set pin 34 to RDY.

I tried to take DF0: out of Storage and throw into devs to use it as an Amiga drive. This didn't seem to work or mount anything, so I modified the list for device 1 instead and still nothing.

I used the Super Image tool, and it attempts to write and fails after the first block no matter what I do.

I DID try the catweasel.device that Ian created and was able to write most of a disk under the Super Image tool but it died at the last block (might be a bad disk). In all cases, if it failed it would send up the Grim Reaper.

I guess my question here.. what is the proper way to set one of these up? Use the drivers that are part of the OS, use the drivers that Ian created or other?

Okay.. got it fixed.

Erased the partition on the drive on my Mac. Booted off of my USB key. Opened up the Media Toolkit, reloaded the RDB and saved it to the drive again. Created a partition, made it non-bootable, and non-mountable.

Booted successfully off my USB key, mounted the drive manually, formatted it, and installed the OS.

Before the last reboot, made it mountable and bootable.

I'm thinking that the system doesn't know how to use the filesystem on its way up - it's telling me to partition as NGFS/01. My x5000 hangs when it sees the disk formatted this way when booting.

If I boot with it say formatted with FAT or whatever, it boots with it in the drive without a problem and mounts it.

The USB drive boots fine and has a boot priority of '1' which means it should be first in line. I went through the startup-sequence and there is nothing exciting in it at all. I don't see any reason why it would even bother trying to look at DH0.

One thing I notice that's different is that during the boot process, without a drive, I get a traditional WB/Kickstart screen for a minute and with it, it dies before it shows it.

I don't believe I overwrote it - I booted off of it fully all of once, and just enough to launch the Media Toolbox.

I believe I can boot fine off of it without a drive in place, I'll double check this morning.

The boot priority seems plausible, I'll check it this morning. The manual states I should put it at '0' for the hard drive.

Picked up an A1222+ motherboard and built up my system today. Got it all ready, put in a hard drive, and booted off the USB key as stated in the manual.

It booted fine, went through the Media Toolbox, partitioned the drive, added the filesystem to it, etc. It asks for a reboot to take effect, sure, reboot off the USB key again as it states in the manual..

On the way up it starts tell me that the hard drive is not a DOS disk.. well sure.. of course it isn't, I haven't had a chance to format it yet.

The problem is, it dies at this part - I get an endless stream of requestors looking for SYS: LIB: etc... since I booted off the USB key, this shouldn't happen - it should know to look for its files there.

I took the hard drive out, put it in my x5000 and formatted it, but I still get stuck in the same spot.

I'm a bit lost. It seems like a catch 22 - I can't format it until I boot up and I can't boot up because I can't format it.

Did I miss a step somewhere?

Just an update..

I'm not sure what it was.. RAM, battery, not installing all the AEON pieces or what... but after that and a reformat of my SSD, reinstalling 4.1 up to Update 3, etc, everything is really, really stable.

So stable that it seemed worth it to register IBrowse 3 finally, and donate to HunoPPC monthly.

I've spent this week messing with the system and really enjoying it so .. thanks for the pointers.

Thanks everyone for the suggestions! I've rebuilt this multiple times, but hadn't tried changing the RAM, battery, or not installing all the Enhancer pieces. I'll spend some time today rebuilding it yet again and see if this helps.

UBoot seems to be 2014.04. That seems.. old. How do I get an update?

Okay, I replaced the battery, replaced the 4GB*2 RAM sticks in there with a single 2GB stick. I'm trying to remember how to get into the UBOOT to find out what version I have (was it M?).

If I were to start this all over on a new drive (I have an extra SSD here), what format should I put the drive in.. and what should I do or not do during installation?

Hey All -

Don't post here much, usually just read. I'm an Amiga user since the late 1980s and way back in 2017/18 I bought an Amiga x5000 setup from Amiga On The Lake as my 'end all, be all' Amiga as my 4000T was getting a bit old.

I'm not a novice when it comes to AmigaOS, but I wouldn't say I'm a complete expert either.

That said, every so often I use my x5000, it crashes so often that I get tired of messing with it and I quit using it for awhile until I get the urge again, etc.

So my question - is the OS inherently THIS unstable or is there something hardware related that might have a problem?

Right now the Amiga is running dual DIMMs for RAM (4GB total I believe, 2GB shown obviously), dual SATA drives and a DVD-ROM drive (main boot is and DVD is on the SATA ports on the motherboard, forget what SATA card I have in there), an RX-570 4GB video card, Enhancer, 2.x, etc. It's been a bit, but I think I have a SB128 sound card.

I've rebuilt this thing from scratch, twice. I just updated to Final Release 3.

I used to attempt to use Odyssey 1.23 beta and if I would do just about anything, it would grim reaper. Now with release 3, it doesn't even launch. It just crashes and the task will hang if not break other browsers from launching.

OWB no longer works due to secure websites.... Netsurf can't seem to find DNS so it says all websites are non-existant. Now I'm stuck with no browser at all.

I try to copy files off a USB stick.. sometimes it works.. sometimes it crashes by locking up the entire computer.

Many programs that I use will tell me I need a certain lib.. which is fine... I can grab it, but the machine crashes when it errors.

I get the lack of proper memory management, but does every issue cause the machine to need to be rebooted or is something just wrong with this? Where do I even start troubleshooting it?

Add another one to the list.. checked out that file, just showed the last place I streamed.

I'm guessing wherever it's pulling its list from has changed?