First impressions of 4.1 Update 1

[spihunter]

OK, nevermind...I see the bi#$%ing now! My bad!

i don't think so (at least with this update). I've read a lot of blaming yesterday on the front page of the most OS4 centric sites ... well, apart some usual fanatic.

The main problem (IMHO) is the lack of official betatersters (they are not paid at all and the OS4 betatester coordinator is kicking out some as well "pretending"  a full job-like time dedication) plus the new join venture about the new mobo.

Face it ... the true and deep betatesting is done by us, the users :-)

Anyway, enjoy it .... Amiga is always been so!

[Matt_H]

Welcome back good old WBStartup directory!

I'm reminded of the old saying, "If it ain't broke, don't fix it" (the way WBStartup has worked for 20 years, that is)

[redfox]

@Matt_H

I used IBrowse the first time and got the corrupted file.  Then I downloaded again using OWB 3.22 and that file was fine.  I used AmiDVD to burn the ISO to a CD-R disc.

The booting issue seems to be isolated to MicroA1-C so far.  Disabling the rear USB ports allows us to boot cleanly with the CD or hard drive.  However, some of us experienced the nightmare first before the temporary fix was discovered.  For whatever reason, the sytem becomes very unstable if all the USB ports are enabled.  We did not have this problem with the previous version of OS4.1.

We don't know if the issue is related to a particular CPU or the MicroA1-C in general.  My CPU is an IBM PowerPC 750 GX.

( I personally have experienced a similar unstable system before.  Shortly after I installed the original version of OS4.1, I unwittingly used the UBOOT Prefs program included with OS4.1 to change some settings to change the hard drive from PIO to U-DMA 5 mode.  My system became extremely unstable and would not boot properly from the hard drive.  It took me 2 days to solve the issue.  I had to reset UBOOT to factory defaults and disable the USB ports and carefully rebuild my UBOOT settings. Eventually I was able to restore my USB ports.  I ran my system in PIO mode for months after that. )

---
redfox

[Matt_H]

@ redfox

Apart from the IBrowse corruption, my installation/bootup was very smooth on an XE-G4. Sounds like a bug in the reworked USB drivers.

@ Framiga

the OS4 betatester coordinator is kicking out some as well "pretending" a full job-like time dedication

That is unfortunate. A smaller/less representative sample of users in the beta pool will inevitably lead to more bugs discovered upon public release. Although maybe it will cut the testing phase from 18 months down to 14

[jsixis]

I'm glad to read some actual feedback on the update... Its seems like everyone on the OS4 centric sites are too busy giving dancing bananas & high fives to actually use the product and point out needed stuff & fixes....

 I agree. Until I get to sit down and actually use one of these "new" amigas I'll just keep using my old amigas and windows when I have too.

[Karlos]

If anybody is interested, I installed it on my A1 XE and posted my initial reaction here.

[cha05e90]

"doesn't support the execution of scripts"

No? Not here. All scripts are executed. No difference between old WBStartup drawer and new WBStartupPrefs. What are you doing wrong?

[Karlos]

"doesn't support the execution of scripts"

No? Not here. All scripts are executed. No difference between old WBStartup drawer and new WBStartupPrefs. What are you doing wrong?

It works fine for me, provided the scripts have a proper icon with the associated default tool.

[Matt_H]

It works fine for me, provided the scripts have a proper icon with the associated default tool.

What default tool did you use? I thought I couldn't get anything going with RX, but it's been a few weeks since I tried and I may not be remembering correctly (and I've since gone back to the "classic" WBStartup methodology, so it's not a big deal).

[warpdesign]

This will no doubt confuse the hell out of new users. Why haven't these tools been updated?

I guess it's because no one had time for that. So the question is more: why hasn't it been removed until something new and useful has been written ? Since it's right now useless and may confuse users

I guess this is because the team needs someone like you

[Karlos]

What default tool did you use? I thought I couldn't get anything going with RX, but it's been a few weeks since I tried and I may not be remembering correctly (and I've since gone back to the "classic" WBStartup methodology, so it's not a big deal).

For AmigaDOS scripts, C:IconX. For ARexx scripts, C:Rx

It used to be the case that the Rx command was in SYS:Rexxc, which doesn't appear to exist any more. Check your path to the executable, mine was still pointing at SYS:Rexxc/Rx at first.

[kolla]

For AmigaDOS scripts, C:IconX. For ARexx scripts, C:Rx

Hm, no. Just use "rx"

It used to be the case that the Rx command was in SYS:Rexxc, which doesn't appear to exist any more. Check your path to the executable, mine was still pointing at SYS:Rexxc/Rx at first.

All the commands in old SYS:Rexxc are reentrant and marked pure, so they can be resident, either manually or by setting the h-flag, why people insist on accessing disk all the time is beyond me.

But then again, this being OS4 ... who knows... :crazy:

[Karlos]

Well, that should also work.

All the commands in old SYS:Rexxc are reentrant and marked pure, so they can be resident, either manually or by setting the h-flag, why people insist on accessing disk all the time is beyond me.

If you call the same command twice the chances are that the command will be in disk-cache memory anyway so it makes little sense to make it resident. Especially if it is used a couple of times during startup only.