AmigaOS 3.2 released!

[rabidgerry]

Originally Posted by Michael

FFS has not changed much, long file name support is provided for higher level FFS versions. So PFS or SFS could be more interesting for some cases.

In the end I just did what I always did for formatting a new hard file/CF card.

Mind you I had to clear out some space on the install disk so I could put PFS3AIO, pfsformat and setfnsize onto the disk.

I guess I was mislead by the Amiga bill video where he says you don't need to mess around with setting transfer rates and all that kind of stuff. Well actually, I did have to mess around with all that in my case then if I wanted PFS3AIO since the FFS isn't much better than the one from before.

[fc.studio]

I've standard OS3.9 with my personal and light setup, stopped about 10 years ago. So I would not come from cwb. Which do you prefer? Do you find OS3.2 lighter and faster?

[crazyc]

Yes, but I was coming from a fully loaded cwb 3.9 setup that I also use on my b1260. So it ran fine on the b1230 without being as snappy. So if 3.2 didn't feel quicker and lighter then I don't know what would be happening.
Anyway.
My advice is as per my other post. Yes I would migrate to 3.2, but allow yourself some time to customise and add bits to round it out before making it your daily driver.
An easily accessible cf card is useful at that point....
Well that is what I have done

[fc.studio]

Thanks

[Lisko]

Originally Posted by fc.studio

I've standard OS3.9 with my personal and light setup, stopped about 10 years ago. So I would not come from cwb. Which do you prefer? Do you find OS3.2 lighter and faster?

I updated my 3.9 setup straight to 3.2 and I think it is the best option as you will also retain some 3.9 goodies like amidock and t.h.e tools menu editor. For simplicity it's advisable to remove deficons from wbstartup before beginning the 3.2 installation so it can automatically install new 3.2 deficons. After installation you can also remove prefs/deficons as the new tool that must be used is prefs/DefaultIcons. You should have to recustomize your startup-sequence if you customized it before. Also remove old modules like scsi.device from devs if you have them, for example if previously you installed bb3&4.

[Rotzloeffel]

Originally Posted by Lisko

Also remove old modules like scsi.device from devs if you have them, for example if previously you installed bb3&4.

This is not necessary, because 3.2 setpatch nore Loadmodule will load older devices as long as you do not use 'the DOWNGRADE option of loadmodule

Also the Tools-Menu is costomysable by the user, editing a simple script. Read the Docs for this

[tech3475]

Just want to confirm, are 27C800 EPROM ok to use in an A1200?

[Swe_Kryten2x4b]

Originally Posted by Rotzloeffel

This is not necessary, because 3.2 setpatch nore Loadmodule will load older devices as long as you do not use 'the DOWNGRADE option of loadmodule

Also the Tools-Menu is costomysable by the user, editing a simple script. Read the Docs for this

The tools-menu is indeed very nice in 3.2. T.H.E as well as tools-daemon can be removed with no loss in functionality (granted, I copied the default T.H.E menu entries as well as the rexx-scripts into the new tool). The only thing missing is a nice GUI to configure it the way you want it.

[Lisko]

Originally Posted by Rotzloeffel

This is not necessary, because 3.2 setpatch nore Loadmodule will load older devices as long as you do not use 'the DOWNGRADE option of loadmodule

Also the Tools-Menu is costomysable by the user, editing a simple script. Read the Docs for this

Yes I know but if I have a nice reaction gui for doing it then why not? It will keep the entries organized.

[fluffkitten]

Just found out how useful 3.2's ability to step through startup-sequence and user startup is for figuring why your system won't fully boot. Given my ability to stuff up those files this is a godsend.

[supercompman]

I seem to have found an issue with AWeb when using a 680000 CPU and OS 3.2. AWeb begins to load, but haults with the error:
Software Failure
AWeb
Program failed (error #80000003)
Wait for disk activity to finish.

In doing some testing, it looks like this is not an issue with a 68020. If I were to guess (and it really is only a guess), it feels like some 68020+ code in the ReAction code somewhere.

AWeb 3.5.09 worked fine on OS 3.1.4.1.

[Michael]

Originally Posted by supercompman

I seem to have found an issue with AWeb when using a 680000 CPU and OS 3.2. AWeb begins to load, but haults with the error:
Software Failure
AWeb
Program failed (error #80000003)
Wait for disk activity to finish.

In doing some testing, it looks like this is not an issue with a 68020. If I were to guess (and it really is only a guess), it feels like some 68020+ code in the ReAction code somewhere.

AWeb 3.5.09 worked fine on OS 3.1.4.1.

Could be anything, but 3.1.4 did not come with reaction, so please test with another set of classes. Does it open the gui or fails earlier? SnoopDOS should give some more hints where it stops

[supercompman]

Originally Posted by Michael

Could be anything, but 3.1.4 did not come with reaction, so please test with another set of classes. Does it open the gui or fails earlier? SnoopDOS should give some more hints where it stops

The GUI does begin to load but halts when "Loading GUI images".



Additionally, I have attached the SnoopDos logs from both 68000 and 68020.


Since 3.1.4.1 doesn't come with ReAction, I was of course using ClassAct 3.3. I'll do some additional testing and post my results when I get a chance.


Thanks in advance.

[Michael]

Originally Posted by supercompman

The GUI does begin to load but halts when "Loading GUI images".

Since 3.1.4.1 doesn't come with ReAction, I was of course using ClassAct 3.3. I'll do some additional testing and post my results when I get a chance.

AWEB APL 3.5 68000 from aminet starts up without problems, just unpacked, no installation.

First, I see you have a problem with missing updated titlebar.image and possibly a mix of some other classes, this could be a problem

[Jope]

Copying some files to an OFS floppy using the copy command in the shell. If there is a write error, you end up in a very very long cancel clicking exercise, ctrl-c in the shell does not help. Taking the disk out results in an endless string of "you MUST insert.." requesters.

[supercompman]

Originally Posted by Michael

AWEB APL 3.5 68000 from aminet starts up without problems, just unpacked, no installation.

First, I see you have a problem with missing updated titlebar.image and possibly a mix of some other classes, this could be a problem

Well, I used completely new storage, created a new FFS partition, and performed a completely fresh, unmodified install of OS 3.2. Using the AWeb-3.5.09-68000.lha archive from aminet and just decompressing it, I am still seeing the exact same error:
Software Failure
AWeb
Program failed (error #80000003).
Wait for disk activity to finish.


The issue is consistently and reliably reproducible on my machine, an NTSC Amiga 500 with the following upgrades:
68010 CPU
Kickstart 3.2
Kipper2k A508 8MB Fast RAM expansion and CF card interface
Full ECS chipset
2MB Chip RAM


Additionally, the missing titlebar.image also appears in the SnoopDos log I created for the 68020 CPU, where AWeb runs just fine as well as when I run AWeb on my Amiga 500 (68010) using OS 3.1.4.1.


Thanks

[klx300r]

in my desktop A1200 I installed OS3.2 with my 3.1.4 roms but afterwards decided to buy new 3.2 roms …question is what files can i erase and what lines do i need to add/edit in my startup-sequence etc?

[bubbob42]

Originally Posted by klx300r

in my desktop A1200 I installed OS3.2 with my 3.1.4 roms but afterwards decided to buy new 3.2 roms …question is what files can i erase and what lines do i need to add/edit in my startup-sequence etc?

None. They will be ignored automatically.

[klx300r]

Originally Posted by bubbob42

None. They will be ignored automatically.

[tomcat666]

Anyone tried os3.2 with the AGS game selector? I get file lock problems on the temporary file that AGS uses to launch games. So after first game is launched the AGS is not able to write to the file anymore and an error that it cannot write the file is returned. This works fine on all previous versions of the OS.