I said sorry because locking up is worse than just a keyboard lockup. It's like accusing someone of farting when they really just sneezed. It always makes it to the main screen but often the mouse and keyboard aren't working. I push the num-lock key repeatedly as it boots. I know the keyboard has locked up when the light quits going off and on. The mouse and keyboard always quit working together. It happens anytime from halfway through boot to the main screen. Doing the installation was a pain because it was so slow and I had to reboot so much. I haven't been able to experiment with a USB keyboard / mouse yet. I'll get to that soon.

he was yesterday online without answering

Quote:

I don't understand sorry. Do you mean that your PS/2 keyboard and mouse stop working wile all the rest of the system continues to work as usual, or that everything freezes and you can't do anything but a reset?

Quote:
Not wanting to drag this into something negative, but apparently my reaction was needed in order for you to give a correct description of what is actually happening.

This kind of information is much more helpful then telling that another OS runs on your machine (which only tells that the hardware appears to be working correctly... for that OS).

You can be rest assured that AROS developers read everything, they just don't have the time doing these guessing games, so i let myself sucker into that because my time is much less valuable then theirs

Quote:
The most likely suspect (without any other feedback, so i'm guessing) is your video-card (or actually the AROS driver for that card). Try to run AROS in vesa mode and see if that help improve stability.

Hello Pioneer,

if you have problems regarding Aros it is best to ask here, amigaworld is more dedicated to AmigaOS. I do not know under which name you are active there and what you proposed but if it was about missing features in AmigaOS people are a little sensible because it was too much asked already in the past. All platforms that are still in development (3.X is not) are "hobby" platforms done by small groups of people in their spare time, that is also and expecially true for AmigaOS despite the impression Hyperion tries to create in public. AmigaOS is propably in the worst situation because of being "commercial" (MorphOS is "half-commercial" and AROS opensource) so basically any development has to be paid (expecially to Frieden brothers and contributors of components). I personally doubt that there is any paid development today and the voluntary contributions are done in spare time by developers not getting any money for it. So I think development at AmigaOS has more or less stalled. That does not justify being unpolite even if you think some ideas have discussed over and over again for years or a question is "stupid". But be realistic, if you compare any platform including Aros with one of the big modern platforms you have to be disappointed, it is hobby and fun, not more and not less and not competition to Mac, Windows or Linux.

Sorry, lock-up isn't an accurate description of what happens. The computer always boots up okay, but at some point the keyboard and mouse stop working. The point when they quit working seems pretty random, not always in the same place. They're both PS/2. I will try different keyboards, including USB.

I have tried many things. I checked the "wipe" box which I imagine removes all the partitions on the drive and frees up the entire drive. It is possible to check the "create" partition box without specifying a size. When I did this I got what I assume are the default partition sizes, since a size wasn't specified: one 8 GB and one 1 GB. I don't have any added USB devices. The CD ROM drive is an IDE drive with the old fashioned flat cable. There is only 1 SATA device, which is the hard drive. I tried the IDE setting instead of the ahci.device, it wouldn't let me create a partition at all. The only added hardware is an AGP 2 video card. Like I said, it's a pretty ordinary HP motherboard. There aren't that many options. It isn't difficult to try almost all of them.

I got the reaction I expected and the same one I usually get on Amigaworld.net. Instead of real answers, I am told I'm just too dumb to work it. When people point out obvious things it isn't helpful. I'm pretty sure the answers I'm looking for aren't obvious and so will never see the light of day. I am left with the suspicion that no one knows the answers and if they do they're keeping them to themselves. So I have two fights, one with the hardware/OS problems and the other with unhelpful comments from fellow sufferers. I plan to explore whatever is available in the package on my own, which will end in disappointment. Then I'll pack it in and wipe the drive with a modern reliable operating sytem and go on to something more fruitful. My questions are purely rhetorical and I thought might generate some conversation that might be interesting to someone. People naturally don't want to hear about things going wrong and prefer nice neat little success stories, which I unfortunately haven't been able to provide.

It's normal to complain when things go wrong. That's the way improvement occurs. It's a crucial part of the development process. Developers often fail to recognize the important role complainers play. I think Europeans probably think Americans are whiny and complain a lot. It's totally true. We always want things to be better.

Apparently ahci.device give issues for you. Please keep this into mind.

If using free space, AROS installer doesn't default to anything other then what you tell it to use. Although i am not 100% sure, i do fail to see why that would be different when using AHCI.device.

So, unless something other fishy is going on i can only guess by guessing you have 9GB of free space somewhere that you have told AROS to use. 8 of which are used by the boot partition and 1GB of which is used by your DH1 setup, just as you told it to use ?


Does your other setup also 'locks' when using vesa mode ? have you tried any of ncafferkey's suggestions that i linked to ? If so, which ones ? what where the results ? Do you also/still use ahci device for that machine ? have you tried in legacy/ide mode ? do you have other devices in that machine that could disturb like a sata cd-rom/dvd-player ? Is one of your USB peripherals perhaps not playing nice ? is there any message on the screen when your system locks-up ? If so, what is that message ?

Instead of playing (yet for me another guessing game) and in case you haven't already. Try configuring your machine and peripherals with the minimal amount of hardware and lowest configuration specs needed/possible in order to boot AROS (properly) and start adding hardware or enable features from there to see if you are able to locate the culprit.

I used the ahci.device. It turns out that it lets me create a partition less than 8 GB's. If I let it create the default DH1 it is 1 GB. This is too small for the stuff it wants to install, so of course it fills up the drive and runs into problems halfway through the install. Should default to something bigger.

I put a HP motherboard that's a few years old in a different case. Dual core, 3 Ghz. Added a 160 GB SATA 2 3.0 hard drive and a AGP 2 video card. 2 GB RAM. Locks up when booting 75 percent of the time. Have to reboot over and over. Ran Windows 10 on same system. No problem.

Quote:
Not that i am aware of.

The only limitation i know of is that the AROS partition which you want to boot from is required to be in the first 128GB (if i remember the number correctly).

It would be a bit difficult to pinpoint exactly what's going on without knowing some more numbers.

Would you be able to share more about which layout your boot device has on which you installed AROS ? You could use a linux tool like gparted for that.