[RESOLVED] X1000 won't boot from HD into Workbench

[nbache]

The best and fastest way to find out is to set up a serial link to another machine and see what the boot process reports there. That should give us a clue.

See the guide on the AmigaOS Wiki: https://wiki.amigaos.net/wiki/Advanced_Serial_Debugging_Guide

BTW, it is not necessarily a problem with the monitor or the monitor drivers. Most likely the boot process just stops for some reason before the display kicks in, so you never get the error on the screen. That's why we need to look for it in the serial log.

Best regards,

Niels

[nbache]

Did you save that log on a Mac? There are no line feeds in it, only CRs, which makes it almost impossible to read. I'll have to find an editor with line end conversion ...

Best regards,

Niels

Edit: Here it is with proper LFs.

[nbache]

It seems to crash in IPrefs, i.e. while loading/setting up Workbench with whatever settings and auto-started programs you have there.

The last loglines before the crash mention the charset having been initialised, but I'm not sure what should happen right after that. And it seems to be quite a bad crash, since Grim Reaper also crashes right after that. Hmm, maybe something with the GUI or Font settings?

You could, while booted from the CD, try to rename your .prefs files in Prefs/Env-Archive/Sys/ one by one and try booting from HD after each. I know, tedious work, but it should lead to more enlightenment :-).

Another possibility, of course, is to create a new installation on HD (assuming you have any unused disk space for another partition) and see how that goes. Then you can either do the above process from there (a bit faster boot), or yyou can try recreating all your settings on the new partition.

BTW, you might catch the eyes of more OS4 devs and beta testers over on Hyperion's forum. Edit: Oh, you were also there already - I got confused. Sorry :-).

Best regards,

Niels

[nbache]

Would running a higher level of debug provide additional useful information?

I doubt it. The debug level is primarily affecting the output from the kernel. But since are not yet sure what the problem is, it could be worth a try.

You probably shouldn't go higher than 4, though, that would be more bother than useful.

Best regards,

Niels

[nbache]

Good - let's know how you fare!

BTW, it could turn out to be one of the things you start with WBStartup, so if you get to the point of restoring that prefs file, and it then fails, you have yet another task in disabling/enabling things one at a time in the WBStartup prefs editor.

Best regards,

Niels