@Futaura

That would explain it, thanks.

The speed of some AnimGIFs in avatars has changed a lot from 2.3 to 2.4. Is there a reason for this? I heard somewhere that there is no specification for the speed of replay, is that correct?

@number6

"GL"? Is that the "Grand Luxe" version?

@sundown

Memtester is not the be-all and end-all of memory testers. I have here a 512 MB registered DIMM that should work perfectly, and indeed I have run memtester on it for three days without a single error being captured. However, it can't reliably run OS4 for any length of time.

It might be because memtester can only test a limited amount of the memory - that part which is not occupied by the system.

[One Of These Days I'll write a proper memory tester that runs stand-alone (without an OS behind it) and can test the whole contents by moving itself, etc. Last time I did that was back in 197x when solid state memory first came on the market and we didn't trust it (!).]

@ssolie

I think that's a little unfair on Eyetech. They probably had no choice in the matter. If you get a Taiwanese company to assemble boards for you, THEY decide where they are going to source the components, THEY decide how they are going to be assembled, etc. If you try to maintain any control over the process, the price and lead time grow exponentionally.

I'd bet that Eyetech were just as surprised as everyone else to see the crummy heat sink held on with double-sided tape. But by then there was no sending them back for a rework - we would have had to wait another six months for a new production slot.

@orgin

Unfortunately the cygnix "SDK" is incompatible with the OS4 SDK. Which is a real bummer.

@aldur

There is an auto update procedure for beta-testers so that they can remain up to date. Whether that will ever be released to the general public remains to be seen.

@rachy

What log file? I haven't sent you anything yet IIRC. I'll send you one now, though.

@Swoop

Hmmm, can't find anything called "Turbostart", nor any mention of it in the manual.

Maybe it's about time I did a clean installation.

"GreenEagle" and I were playing with his machine today and I was showing him that whenever you boot the machine, you can't print through Turboprint unless you call up the TurboPrefs and select "Save". You don't have to change anything, just "Save" it. Turboprint will work fine from then on.

I remember this same problem from back in the OS3.9 days, so it is nothing new. We ran Snoopy and looked for any new files or ENVs after saving the prefs, but found nothing.

Has anyone found a way to make the settings permanent, so that you don't have to open TurboPrefs after each boot and reSave?

@rachy

The "0x4E8" is the DAR (every time). It is not always reproducable (only happens about once in five starts), but the crash is identical each time. It MIGHT be the first time that Petunia is used - YAM is the only other 68K app that I use soon after booting. I can send you a log if you would like, I have one saved here.

After the crash, the process can not be continued (without crashing again) and I have to reboot since resources are locked, so it is really annoying.

BTW, I never had this problem with IB 2.3, this crash is new to IB 2.4 (which doesn't mean that it's a bug in IB or Petunia, could easily be something else).

Sorry, being a little repetitititititive here.

Well, I disabled Petunia altogether (commented out the line in Kicklayout) and after a week I had no IBrowse failures at all.

Within days of re-enabling Petunia, I get the same 0x4e8 crash again on starting (about once in five starts).

I'll try the prefs suggestions.

@ssolie et al

The days of visionaries (back in the 1980s) are gone, just as the all-knowing Dr. Mack who looks after the village in the mountains has gone, just as the garage mechanic who could fix any car has gone.

These days software and hardware development is so specialised (as is medicine or automotive engineering) that no single person can possibly make as much impact as a qualified, trained team of experts.

We are lucky to have some qualified experts working on OS4. We could use a whole lot more, but spare us from the experts of the 1980s. These days we need experts of the 2000s.

@Snuffy

If you look closely on the card, you will see two pins labelled "LED" or something similar. Remove the connector from JP3 on the mobo and transfer it to those pins on the SiL card.

You might have to extend the wires to make them reach. Don't worry about getting the plug the right way round, if it's wrong it just won't light up, but it won't cause any damage.

The screen blanker is not related, you must have some other problem there. Check the Prefs/ScreenBlanker.

@Chris

It has been reported, it is in the list of bugs to be fixed, but it's a bit far down on the list of priorities.

[edit] It's also in an area of code where mortals fear to tread because of the danger of breaking even more stuff.
[/edit]

@lazi

Regardless of the risk of electrical damage, the PS/2 protocol depends on polls and replies in a continuous stream, and there is no provision for recovery from lost polls.

So if you unplug the device, the software in the PC won't know what to do, and when you plug in a new device (or even the same one), there is no guarantee that the two "ends" will be able to start talking again. You need hardware on the motherboard to signal the software that the device has been disconnected, then reconnected, and software to recover from it. None of these features is listed or demanded by the PS/2 spec, and makers don't include stuff that they don't have to.

@hnl_dk

Hi Henning,

I had all of those already, but BetterString was new, so I'll install that and see what happens. Not going to install "The Bar" until I know more about it.

Grr, this is as bad as Loonix - having to chase all over the world to find the "latest versions" created by unknown people, without any authority behind them. Who knows what they do or how they behave under OS4?

@spotUP

Quite possible. All the libs that you have to fetch and install are PPC, but many supplied with MUI are still 68K.

The DSI I get on starting is always from address 0x4E8. It would seem that "it" is writing to 0x4E8(something), while "something" is null (r8 in the dump).

On the other hand, the emulated 68K code shows nothing remotely like 0x4E8. Maybe the offset is something internal to Petunia.

Anyway, I'll run without Petunia (yawn) for a few days and see if I get any similar crashes.

@Vader

OK, I'll disable Petunia for a few days and see if it still crashes.

How "default" do you mean"? I'm running IB on its own MUI public screen, but otherwise as it was in the box. Is that OK?