Some OS4.1 bugs

@MichaelMerkel

It might be interesting to run a DirDiff on your Kickstart dirs on those two systems, plus perhaps Libs, Devs, Classes, Sobjs?

Best regards,

Niels

@m3x

I tried to email to an address I found from your profile. I got answer: "Delivery Status Notification (Mail Delivery Delayed)".

@thread
I get endless yellow alerts when trying to kill that test program with GR. Maybe we all can investigate this a little further.

@thread:

1) I can confirm the endless recoverable alerts here

2) Can anyone confirm the multi-assign bug that I mentioned earlier? (Read prev. post).

@thread:

Sadly or happily I can confirm it here too. On A1 XE ad Sam440Flex

@all
I would appreciate if people would create their OWN threads for their OS4 problems, because I get spammed by "new message!" emails every time someone posts something here (even though it now has nothing to do with my posts).

@Rigo

umisef put it quite well here.

Btw. it seems to happen more frequently, or possibly only, on A1, not on SAM. Could it be some A1 specific driver or module?

@Deniil

I have a SAM-flex, and I have the same problem


Quote:

I withdraw my statement, as I cannot produce this problem anymore here. Maybe an update 2 fix

@Deniil

Well, as I said before, I tried it on my Sam and my XE, and both systems do not exhibit the symptoms described.

Simon

@ChrisH

Sorry about that... But maybe you need to name your threads very specifically if you like them to stay onto your initial topic...

"Some OS4.1 bugs" sounded like a very generic and open thread for all kinds of OS4.1 bugs so I just used it.

@Rigo
Quote:
Great! Squashing bugs will certainly improve everyones perception of OS4 reliability. I just wish that we could get more "minor" updates out to the public for further testing. The current reporting/fixing/releasing cycle has been a tad slow in my view.

@xenic

Hopefully, that can change in the near future...

Simon

@MichaelMerkel

Quote:

i started with my clean os4.1upd2 partition. as written - no problem! no gr crash.
i then copied some drawers from my normal workbench partition over to the clean one and rebootet - well gr crashed!

recovering the clean partition i copied over drawer by drawer and tried it. the prefs drawer seems to be the culprit here.

ok - investigating the prefs drawer. it of course contains the env-archive drawer. copying over everything *except* the env-archive drawer - reboot - test - no gr crash!

so i believe that some env prefs is causing this.
i continued and found one possible problem:
contextmenu.prefs. at least i thought so.

using the "clean" one - no gr crash. using my one - crash.

but on my normal partition gr also crashed without any commodity running... and that is quite strange. so it cannot be contextmenu.prefs?!

i'm lost currently.

fact:
1. on a clean os4.1upd2 partition gr never crashed
2. on my partition it very well does - even if no startup-sequence and no wbstartup has been run.

that one is very strange!!

maybe i can investigate a little more tomorrow - or later. let's see. i like such "problems"

regards...

@MichaelMerkel

Another idea, after reading the above strange symptoms:

If you have disk space to spare, try creating a new boot partition, same size, blocksize and filesystem etc., and copy everything over from your current one (the one that crashes). Then set the new partition to have the lowest boot priority; depending on your KickLayout and other references (e.g. in prefs files) you might need to also relabel the partitions so the new one gets the volume name the old one had.

This is intended to determine whether the problem is caused by some problem in the file system structure of your current boot volume. It's the only explanation I can think of right now which fits the facts you state.

Best regards,

Niels

@nbache

Quote:

well, the clean os4 partition already is a separate, bootable partition i always have this is place to check programs which cause problems and to see if this lies on my special installation or not.

regards...

@MichaelMerkel

I would be nice to know which Kickstart modules you have disabled and enabled different between your working and non-working configurations ? I get also those endless yellow alerts even when running system without Startup-sequence. What prefs files might any Kickstart modules read. F.ex. IPrefs is run in S-S.

@MichaelMerkel

Quote:
Yes, but I'm talking about something else: Try creating an exact copy of your normal system disk, on a fresh piece of the disk, and use that to boot from instead of the original. If GR still crashes, you know it has to do with one of the files, if not, it must be a disk or filesystem error on your original partition -- in which case you could reformat it and copy back the contents (which might solve it if it's some sort of obscure filesystem error) or just use the new copy as your system partition in the future.

Best regards,

Niels

@TSK

Quote:

they are identical

regards...

That Grim Reaper and endless yellow alerts problem:
- If I boot from 4.1 Update1 CD then GR works as expected/correctly
- If I do soft reboot with Update1 Kickstart in memory but all the rest loaded from Update2 on hard drive then GR works as expected/correctly
- If I power off - power on and boot from Update2 on HD then endless yellow alerts with GR
- Then rebooting again from Update2 on HD, delete/rename ENVARC:sys/locale.prefs, delete/rename ENV:sys/locale.prefs, Expunge locale.library then GR works correctly (as expected) ! I'm using Finnish locale always.

Public 4.1 Update2:
- locale.library 53.3 (19.7.09)
- GrimReaper 53.2 (30.8.09)

Public 4.1 Update1 CD:
- locale.library 53.3 (19.7.09)
- GrimReaper 53.2 (30.8.09)

New Kickstart modules in 4.1 Update2:
- newlib.library 53.10 (3.3.10) (in Files_AmigaOne)
- dos 53.58 (21.4.10) (in Files_NoArch)
- elf.library 53.12 (3.4.10) (in Files_NoArch)
(Those are correctly installed on my SYS: .)

Older Kickstart modules in 4.1 Update1 CD:
- newlib.library 53.9 (13.1.10)
- dos 53.48 (21.12.09)
- elf.library 53.10 (13.12.09)

- Verified: If I put my locale.prefs back to envarc:sys and env:sys then I'll get endless yellow alerts again.

That weird file names when backuping a HD partition:
I guess it's problem of automatic Workbench drawer updates because it looks like real file names are correct. If I select Update from Window menu of the Workbench after file copy process have finished then it displays file names correctly.

@MichaelMerkel

Can you confirm what I found ?