OS crash on real Amiga, but works fine on WinUAE

[superfrog76]

I am getting a weird issue here....I do not have the CD interface for my 1200, so I am using the PC to install 3.9 on my CF card.

The partitions seems fine, I tried to boot from Install disk, and I can see the drives and contents of the various partitions. But when I put the CF card in the Amiga, it just goes in guru, as soon as it boots, the power light blink and it restart.

It seems to work just fine on WinUAE.

This is what I did: Installed 3.1, updated to 3.9, installed ClassicWB for 3.9, installed some applications (like assembler, WHDLoad, Dpaint and so on).

Is there something that I can do to troubleshoot the issue, or do I have to start all over, installing 3.1 -> 3.9 -> MagicWB -> software; and see in which stage it stops?

I miss the nice modern crash reports

[Oldsmobile_Mike]

Not sure if it helps, but if you use the "make emergency disk" option off the 3.9 CD, you can install 3.9 directly onto a blank hard drive, without having to install 3.1 first.  At least it'll let you skip a step!  

[superfrog76]

Good to know! I thought that I must have 3.1 installed to put 3.9 on it.

Will try that right now; so far it seems that base 3.1 is not the problem, so I can just move on the 3.9 install.

[AndyFC]

I had a similar problem when I first transferred my 3.1 install on 2.5" Hard disk from WinUAE to real Amiga.

I plugged the Disk back into my PC, reduced the Maxtransfer Rate in HD Toolbox via UAE and it worked after that.

[superfrog76]

I had a similar problem when I first transferred my 3.1 install on 2.5" Hard disk from WinUAE to real Amiga.

I plugged the Disk back into my PC, reduced the Maxtransfer Rate in HD Toolbox via UAE and it worked after that.

In my case it seems that the problem is the boing updates on the 3.1 system.

Do I need them after all, if I am going for the ClassicWB install?

Ironically my 3.1 that I had on my 2.5 HDD is working flawlessly

Also I am curious....do I really need 3.9 after all, or is enough to have just 3.1 with ClassicWB? I know that it is a matter of preferences, but I wonder if it is just a waste of time to use 3.9 (btw I have a 030/50 with 32 mb as expansion card, not even sure if that is enough to run 3.9 decently....it runs fine on my dual 8 core, but that's not fair LOL)

[som99]

In my case it seems that the problem is the boing updates on the 3.1 system.

Do I need them after all, if I am going for the ClassicWB install?

Ironically my 3.1 that I had on my 2.5 HDD is working flawlessly

Also I am curious....do I really need 3.9 after all, or is enough to have just 3.1 with ClassicWB? I know that it is a matter of preferences, but I wonder if it is just a waste of time to use 3.9 (btw I have a 030/50 with 32 mb as expansion card, not even sure if that is enough to run 3.9 decently....it runs fine on my dual 8 core, but that's not fair LOL)

I have the same problem on my Amiga 1200, I got a CD-Rom on my Amiga so didn't have to install from an emulator but the BB2 rom update do not play nice so if i rename it or edit startup-sequence it boots (works in WinUAE with update).

I run ClassicWB 3.1 on my 030/42MHz 64MB ram and I have no reason to use 3.9

You can install on real amiga without a CD-rom drive using a ISO.
Just download and use this:
http://thomas-rapp.homepage.t-online.de/Start.zip (Credit to Thomas) It also works for all CD games I have tried beside Exodus: The last war (can't even get that *?#@**?#@**?#@**?#@* to pass CD check when using a real CD and CD-rom drive)

[bitman]

have you all checked that you have Kickstart 3.1ROMs in your Amiga (required by 3.9)?

[nicholas]

I had a similar problem when I first transferred my 3.1 install on 2.5" Hard disk from WinUAE to real Amiga.

I plugged the Disk back into my PC, reduced the Maxtransfer Rate in HD Toolbox via UAE and it worked after that.

Good advice.

Also as others have said, make sure you have 3.1 ROMs. If not, use a Blizkick type tool to launch the 3.1 ROM from the first line in the startup-sequence.

[som99]

have you all checked that you have Kickstart 3.1ROMs in your Amiga (required by 3.9)?

Yepp I got 3.1 roms, but I don't need a solution since I have no need for 3.9 I was just replying to the thread starter that I have had the same issues in the past.

[Oldsmobile_Mike]

Also I am curious....do I really need 3.9 after all, or is enough to have just 3.1 with ClassicWB? I know that it is a matter of preferences, but I wonder if it is just a waste of time to use 3.9

I don't like ClassicWB, feel like it's too bloated.  With enough trial & error I can typically build in only the customizations that I want onto a clean OS install, and I feel like it's more fun and you learn more about your system that way.  Re: 3.1 vs 3.9, that depends on what you want to do with the system?  3.9 does require more horsepower but it also rolls up a lot of the updates you'd otherwise need to find hacks and patches for to do in 3.1.  Still, a 3.9 system will probably need a fair amount of updating, also, if you're looking for a more "modern" experience.

Or if you just want to play games and use WHDLoad, 3.1 is fine, LOL.  

This is a pretty good list here, there's also a list on the same site to "make 3.9 like 4.1".  Whatever else you do, make sure you start with Peter K.'s icon library.  It's a little tricky to get into 3.1, but well worth it.

http://lilliput.amiga-projects.net/TechDetails3.htm

[Thomas]

I am getting a weird issue here....I do not have the CD interface for my 1200, so I am using the PC to install 3.9 on my CF card.

The partitions seems fine, I tried to boot from Install disk, and I can see the drives and contents of the various partitions. But when I put the CF card in the Amiga, it just goes in guru, as soon as it boots, the power light blink and it restart.

It seems to work just fine on WinUAE.

This is what I did: Installed 3.1, updated to 3.9, installed ClassicWB for 3.9, installed some applications (like assembler, WHDLoad, Dpaint and so on).

Is there something that I can do to troubleshoot the issue, or do I have to start all over, installing 3.1 -> 3.9 -> MagicWB -> software; and see in which stage it stops?

I miss the nice modern crash reports

Most likely your boot partition is unreadable on the real Amiga. It must be smaller than 4GB and completely inside the first 4GB of the drive.

To emulate the same behaviour in WinUAE make sure the drive is connected to IDE0 controller, not to UAE controller.

If you want to make one 8GB partition which is bootable, you have to use a third-party file system, either PFS3ds, PFS3aio or FFSTD64.

[bbond007]

What I typically do is boot from 3.1 floppies and partition(don't forget 0x1fe00 maxtrans) and install WB 3.1/PFS. Make sure it boots, Then switch the card over to my PC and go from there with AmigaForever/UAE and install ClassicWB or 3.9.


I have never had an issue taking that additional step, however I have run into the same type of issue just UAE from the get-go. Also that method allows me to do the FastATA split thing to see multiple 4GB drives.

Hope that helps...

[superfrog76]

Som99: Thanks for the hint; I was not aware that you can use a cd on the real amiga with that method.

Bitman: yes,I do have 3.1 roms I am not that beginner LOL

Mike: thanks for your suggestions...once I used to put my hands anywhere in the OS and write custom startup sequences...but that was various decades ago Nowadays I need to start from scratch and re-learn how did I used to do all that stuff so easily

I've reached the point that I really don't want 3.9....I had it for few hours on my real miggy, and it was a pain...even with 32 Mb it is slow, the chip memory went down to 400K (but the fast ram was untouched...not sure why, since I remember that the chip ram was just used for chipset work, and the Amiga is simply running the OS).

I am planning to use the Amiga for games, but I would like to learn how to write programs for it, so with that scenario, my 1200 with 3.9 is wasted.

I have also noticed that with ClassicWB, nothing WHDLoad works....I get the tedious error 205, which seems legit, since the chip memory available, once everything is running, is down to 1.6 mb, while from my understanding, WHDLoad wants the full 2 mb to run most of the games.

At this point I am going for 2 partitions with different OS: the first, as small one (100 Mb probably), with just the basic stuff like 3.1, music player and WHDLoad, to play games; while the second with ClassicWB will be used for everything else...I can always boot with the boot selector, so it is not a big deal

Unless you know how can I just run one partition with ClassicWB, and at the same time not have errors because of low memory.

Thomas: I am not sure that the partition is the issue; it works fine when you put 3.1 or 3.9 vanilla on it, but not when you put on the boing updates; the partition is barely 500 Mb, and it is the first partition of the disk, so it is in the first 4 GB (plus if I boot with the install disk or WB disk, the partition is there; it just crash when it is booting).

Agree, I will probably install a different file system (I have a different thread on the topic), since I would like to avoid the train wreck that I have already experienced....my partitions just got corrupted twice

BBond: thanks for the info, I think that I prepped the card on the real amiga, and then moved it on the pc to install the rest of the applications (4 Gb of games and demo done on the miggy is pure madness; unless you have a whole day available )

I will try to prep it again, but if I use 3.1 install disk, I will be stuck with FFS, while I am planning to put a different FS on the drive. I have to study more about the best way to put the new FS on it.

[Oldsmobile_Mike]

Mike: thanks for your suggestions...once I used to put my hands anywhere in the OS and write custom startup sequences...but that was various decades ago Nowadays I need to start from scratch and re-learn how did I used to do all that stuff so easily

I've reached the point that I really don't want 3.9....I had it for few hours on my real miggy, and it was a pain...even with 32 Mb it is slow, the chip memory went down to 400K (but the fast ram was untouched...not sure why, since I remember that the chip ram was just used for chipset work, and the Amiga is simply running the OS).

I have also noticed that with ClassicWB, nothing WHDLoad works....I get the tedious error 205, which seems legit, since the chip memory available, once everything is running, is down to 1.6 mb, while from my understanding, WHDLoad wants the full 2 mb to run most of the games.

I hear that!  I took a 10-year break from actively owning any Amiga systems, but it came back to me... slowly.  

There are a couple settings in 3.9 that need to be changed to tell it to use fast memory (or "other" memory) instead of chip memory.  On a typical setup for me I've got about 75% of my chip mem free, this after loading a high-res laced + overscan 16-color Workbench with lots of utilities, and haven't had any problems running WHDLoad games.  Before I had a Megachip in both my systems the only game I found that wouldn't run was Cannon Fodder (required 1.1MB chip).  Maybe try posting some specific games you're having issues with, see if anyone else has the same?  Also the docs (included, depending on where you're downloading your games from) usually list the chip ram requirements.

[Dandy]

In my case it seems that the problem is the boing updates on the 3.1 system.

Are you sure?
I know of "BoingBags" for AmigaOS 3.5 and 3.9 - but for 3.1?
Never heard of a BoingBag for OS 3.1 ...

Also I am curious....do I really need 3.9 after all, or is enough to have just 3.1 with ClassicWB?

I'd say that depends on what you prefer:
Minimalist Workbench = OS 3.1
WB 3.1 + some 3rd party tools like e.g. AmiDock, some eyecandy like backdrops and so on = OS 3.9

I switched to OS 3.5 and then to OS 3.9 - and never regretted it. I will never go back to OS 3.1 - I prefer the OS 3.9 look & feel...

I know that it is a matter of preferences, but I wonder if it is just a waste of time to use 3.9 (btw I have a 030/50 with 32 mb as expansion card, not even sure if that is enough to run 3.9 decently....it runs fine on my dual 8 core, but that's not fair LOL)

[/QUOTE]

On a 030/50 OS 3.9 is a bit slow (my old A1.2k has 030/40). On my A4kPPC with 060/50 it really flies...