@amigamia

Please try if 64-bit version is also giving you these issues. There was a few bugs fixed in vmwaresvga.hidd after 32-bit release and one of them was causing issues similar to what you are showing. This however was not happening in VESA mode.

Yes, 64bit version does not have the same problem. Also, the fix provided by AMIGASYSTEM also works on 32-bit.

Has anyone tried AROS 64 on Dell Latitude D520 yet?

Hello.
While reading the AROS One user guide, I saw that there is a lighter alternative to Wanderer in a "bare" Workbench. I wanted to see what that looked like and ran the Workbench program, which, I assume, altered my startup sequence to start it after boot instead of Wanderer. Many programs rely on Wanderer & co to be running, so I'd like to get those back up. All I did was run Workbench and reboot. Is there any way to get the original startup sequence back? Maybe change or remove a preference file? Just running Wanderer from the shell doesn't work because it requires other things to be running before it can start.

There are no applications on AROS One that can lighten the system and create your problem.

There is ‘Workbook’ which, when used instead of Wanderer, starts a lighter system. To do this, in the startup sequence, the “Wanderer” command at the end of the startup sequence must be replaced with ‘Workbook’.

Once you have done this, you will have a lightweight Workbench, a system that I do not recommend because it no longer makes sense today, given that Wanderer is very fast even on old PCs. Furthermore, ‘Workbook’ does not work well, so I will probably move it from the System folder in C.

In your case, you did not tell me exactly what you changed. If you changed the startup sequence, replace it with the one from the ISO!

Yeah. I did exactly that. I ran Workbook (forgot what it was actually called) and then it altered my startup sequence to use it instead. So, I should get one from the ISO and replace it?

It's easier if you replace the startup-sequence with the one from the ISO. If you want to know where you went wrong, attach your startup-sequence here and I'll check it out!

I'd love to do so if I could locate it. (Though I assume there is nothing interesting there, it's just adjusted to run Workbook.)
AROS:S is simply not present. It is on the live USB drive, but not on my system. Do I copy the whole directory? Did Workbook just nuke it altogether?

(Looking at the scripts, I might not need ALL of them, but surely some of them)

Trying to boot via Early Startup Control without a startup sequence produces, yes, the same thing as I was originally greeted with. Workbook nuked my startup script (and the whole S directory) as it seems. Awesome!
Please tell me which scripts I need for a correct boot. Copying just the startup sequence loads Wanderer, but creates errors on trying to load most programs, mostly library complaints.
EDIT; Tried to copy the whole directory. Looks fine. Seems one does need all of it after all :-) Things now run without issue. Fixed! (Looking at it now, it didn't even run Workbook. It was just loading without a startup script at all)

Is there any way to check system logs? Upon running it again and rebooting nothing happened, so I'm not sure what actually happened here. Was it a one off thing? Did I do something? I don't think I did anything that could make that happen afterwards. Huh.

Never happened. To help you, I need to know what you changed. Did you replace the startup sequence with the one from the ISO?

Can you make a video to show what happens when you start AROS One?

I don't think I need help with this anymore. Transferring the S folder from my live USB fixed my issue. Something happened to make the S folder disappear entirely — I attributed this to running Workbook, but was unable to replicate it after fixing, so it could've been something else/user error. If it happens again with a clearer cause I will write about it here. (Though getting action logs — are writes recorded? — could be helpful in actually settling this.) I don't think I did any direct directory manipulation preceeding the reboot upon which I found something was broken, but I did play with window sizes of programs — including the directory viewer — could I have accidentally selected and removed it? Are there shortcuts to item deletion?

Another (unrelated) problem I must note is that some third party programs run incorrectly. E.g Sokoban throws a stack out of range error when trying to run it. Is this universal? Much of the software was ported years ago and doesn't get updates. Is it having problems running on newer versions of AROS?

When changing the icon, I probably forgot to increase the stack. Sometimes, for some reason, the stack is low, but in this case, the problem can be solved by increasing the stack in Tooltypes Icon, see screenshot.

If you are not familiar with how to do this, go to the icon properties:

- Right-click on Icon
- Information
- Stack

Wow, I can do that? Thanks!

@AMIGASYSTEM

You PM inbox is full. I can't send you another PM.

I have increased the inbox limit. Try again

I emptied it three hours ago when deadwood reported it. I only have two messages; the inbox is almost empty.

Thanks for increasing the limit

Since AROSOne 1.1 still has the OWB icon with the tooltype from the 32-bit version:



I would like to remind everyone that in order to unlock the full speed of OWB on 64-bit, the tooltype should contain:



The MSE entry is optional and causes YouTube to use a more advanced video player.