Boing bag 2 - no mouse/keyboard?

[rvo_nl]

Hi. Installed OS3.9 Boing bag 1, then Boing bag 2. Ofcourse Ive turned power off. After reboot the mouse and keyboard didnt work although the workbench seemed to be 'alive' (no lockup). In early startup they both work, ofcourse.

Perhaps I missed something: was it smart to select YES when asked to install the ROM Update for BB2?

[Matt_H]

What other hardware do you have? That'll determine whether/how you can use the ROM update.

[rvo_nl]

What other hardware do you have? That'll determine whether/how you can use the ROM update.

I was hoping it would turn up in my signature, sorry:

[rvo_nl]

I tried again and this time I was able to move the mouse for a split-second. so the system locks up. Ive renamed wbstartup to see if that helped, but it didnt.

[rvo_nl]

no progress at all. Ive noticed after installing the Boing bags some files in devs: are added or renamed. For example, NSDPatch.cfg-BB3.9-2 etc. Do I have to rename them so they are loaded? Or are they called by their new name? Is Setpatch taking care of this?

And then there's still the question of the new ROM Update that came with BB2: is it safe to install it? Could my problems be caused by it?

[matthey]

Ive noticed after installing the Boing bags some files in devs: are added or renamed. For example, NSDPatch.cfg-BB3.9-2 etc. Do I have to rename them so they are loaded? Or are they called by their new name? Is Setpatch taking care of this?

DEVS:NSDPatch.cfg is the one used by SetPatch. Rename newest NSDPatch.cfg to this. Don't expect this to fix your problem.

And then there's still the question of the new ROM Update that came with BB2: is it safe to install it? Could my problems be caused by it?

The ROM update does cause problems on some Amigas. It's easy to try without it. Use the SetPatch switch or rename "DEVS:AmigaOS ROM Update" temporarily.

[rvo_nl]

thanks, but that didnt help at all. will reinstall os3.9 + boing bags and select NO when asked to use the rom update. might take a few days.

[tone007]

or, delete DEVS:AmigaOS ROM Update

That's the ROM patch file that gets loaded.

If that doesn't fix your problem, it's something besides the ROM update.

[rvo_nl]

hi, after some fiddling I found out the problem is Iprefs. Or perhaps some library that is used by it and is updated by boing bag 2. leaving iprefs out of the startup-sequence works. replacing it with the one that came on the os3.9 cdrom did not. any other ideas?

[matthey]

Maybe there isn't enough stack for Iprefs. Too little stack caused problems with some AmigaOS 3.9 setups. You should probably check that you have these file versions...

IPrefs 45.13
setpatch 44.38

The SetPatch is important because it sets the stack higher for some tasks. Next you can try upping the stack with the stack command early in the S:Startup-Sequence before IPrefs but after SetPatch...

Stack 4096

This is not necessary on most AmigaOS 3.9 setups including mine. You might try the bug fixed AmigaOS 3.9 unofficial updates which add some stack to some modules that may be interacting with Iprefs. These also fix some bugs and I have been using without problems for quite some time. Info is here...

http://lilliput.host-cafe.com/start.htm

[Mugo]

As said before, your problem relies in the Amiga ROM Update file in Devs: folder.

The version installed with BoingBag 3.9-2 is incompatible with some hardware configs. I had a very simillar config, and had problems with this ROM Update.

Just look in the Devs folder, there should be an Amiga ROM Update.old or something (can´t look at my miggy right now), that´s the previous ROM Update. Probably the BB1 one. Just rename or delete the current ROM Update, and remove the .old (or anything like that) from the previous update filename.

Remember you have to power cycle your miggy to make the changes current, as the ROM Update is installed as a resident module.

Regards.

[rvo_nl]

Mugo, I already deleted the ROM Update, before I found out it was Iprefs.

Matthey, pretty interesting. Will try this out tonight.

[rvo_nl]

well, not much luck so far. os3.9 starts completely normal when I leave Iprefs out of the startup-sequence. when I start it from workbench, instant freeze of keyboard/mouse. no response when cdrom is inserted either.
 
increasing the stack didnt help. Ive checked setpatch and iprefs versions and made sure Im running the ones matthey mentioned. Ive tried applying those 'boing bag 3' patches, but I didnt find them very useful, to be honest.
 
tomorrow I will try using fastiprefs instead of iprefs. somehow I remember that was important back in the days. but I doubt it will do much, the iprefs of os3.9 is updated for a reason, I guess..
 
does anyone have some other ideas? for example, deleting the iprefs settings from env-archive?

[zipper]

I sometimes had problems with the background picture/picture datatype crash causing similar symptoms.

[Mugo]

@rvo_nl:

Did you renamed the old Amiga ROM Update to "activate" it?

If you didn´t, this can be your problem. This update applies some very important patches.

Also, i don´t remember if the BB2 update the iPrefs. But usually an iPrefs problem is caused by something else, and not the iPrefs itself.

iPrefs calls a lot of other functions and programs. Can be any other 3rd party patch too.

Good luck.