AmigaOS 3.2 released!

[AMIGASYSTEM]

Originally Posted by Michael

Don't worry, 3.2 eggs do not waist valuable ram, take rom space or even use any harddrive space. How could that be? Well, only time will show...

So if there is nothing in RAM, KickStart or HD, should it be hidden inside some system file? what should be found an image, a sound or what?

[jbenam]

Since Michael specified "hard drive space" I guess that it's something that won't get installed on the HD, and as such will remain on the installation media itself (either CD or Floppy)...

[AMIGASYSTEM]

Yes I had suspected Floppies too, but now OS.3.2 is to be considered a HD OS, I don't think there are many people using OS 3.2 with just floppies, it would be a pain to operate (slowness and uncomfortableness).

Speaking of OS 3.2, I've created a new OS4 style VisualPrefs+Birdie Skin with the gadgets style of the "PaperBlue" Skin plus the 3.2 Logo on the Title Bar.

[Romanujan]

@AMIGASYSTEM Does it contain all the new OS 3.2 gadgets? Is it available for download?

[AMIGASYSTEM]

No I created and customized the VisualPrefs/Birdie Skin inspired by the skins attached, what I did is change the background to the window and gadgets for closing, resize etc..


https://aminet.net/package/pix/theme/os4theme


https://aminet.net/package/pix/theme/PaperBlue


With the same technique I have created a Skin in style OS4 also on AROS 68k, all you need is a little patience and a Good Graphics Program

[systmcrsh]

is this the right thread for bug reports?

i'm not sure if this is a bug or not... but the following worked with 3.1 (and i'm %90 sure it worked with 3.1.4 too, < but i'm not %100 about 3.1.4, but def %100 about 3.1)

i wrote an installer script for some software that i wrote that would take the installation path that the user chose during installation, and installer would write a script, and set it executable, that the user could run (by double clicking) after installation. the script basically just creates assigns, adds paths, etc, based upon the path that the user chose to install the software. there is no icon associated with it.

^ i prefer doing it this way because its non-permanent and non-destructive... a simple reboot and the assigns, paths, etc are erased...

after 3.2, the script that the installation script creates is no longer executable. it opens with text edit.

i suppose i can just create an icon for the script and include it in the installation package from now on, but i thought it might be worth mentioning here as it previously worked with 3.1 and earlier...

relevant part of the installer script:

; user-script
(textfile
	(prompt
		"These instructions will be added to "(cat quote Inst_Dir )"/snacky.run" quote
		" so that your system will be properly configured to use SNACKY."
		newline
		newline
		(cat user_assign)
		(cat rexx_assign)
		(cat user_path)
		(cat user_extra)
		(cat "RUN >NIL: RexxMast" newline)
		(cat "RUN >NIL: "quote Inst_Dir"/bin/nsmport"quote newline)
		(if (= nsm_exists true)
			(cat "RUN >NIL: "quote Extra_Dir"/OctaMED.nsm"quote newline)
		)
	)
	(help @textfile-help)
	(dest (tackon Inst_Dir "snacky.run"))
	(append
;		(cat user_run)
		(cat user_assign)
		(cat rexx_assign)
		(cat user_path)
		(cat user_extra)
		(cat "RUN >NIL: RexxMast" newline)
		(cat "RUN >NIL: "quote Inst_Dir"/bin/nsmport"quote newline)
		(if (= nsm_exists true)
			(cat "RUN >NIL: "quote Extra_Dir"/OctaMED.nsm"quote newline)
		)
		(cat "ENDCLI" newline)
	)
	(confirm)
)
; end user-script

; set executable
(if (= (exists (tackon Inst_Dir "snacky.run")) is_a_file)
	(protect (tackon Inst_Dir "snacky.run") "+s")
)

[Steady]

@systmcrsh

That isn't something that was changed in the Installer. I will raise a bug and have a look at it using your sample script.

What file system type are you installing to? FFS?

[systmcrsh]

Originally Posted by Steady

@systmcrsh

That isn't something that was changed in the Installer. I will raise a bug and have a look at it using your sample script.

What file system type are you installing to? FFS?

yes, ffs.

to be clear, everything above the "; set executable" line works as expected... its just setting it executable doesn't seem to work anymore. ("+s")

in 3.2 double-clicking the resulting file opens with text edit instead of prompting the user to run it.

*edit* i can provide the entire installation script or installation package if thats helpful too. thanx!

[Thomas Richter]

This looks as if the system grabs a default icon (DefIcons system) for the text file, whose tool is the text editor. Thus, try to remove DefIcons to see whether that resolves the situation. You can also just include an icon (with IconX as tool) for the script you create, this should also do the trick.

[AMIGASYSTEM]

I confirm, OS 3.2 through "Deficons" associates to text files the command "SYS:Tools/TexEdit".


@systmcrsh

To make the installer work you have to replace the command with "Installer", no need to add paths.

[Thomas Richter]

Actually, now that I think about it, it is more a deficons configuration issue since files with the S bit set should not get the editor as default tool, but IconX.

[systmcrsh]

Originally Posted by Thomas Richter

Actually, now that I think about it, it is more a deficons configuration issue since files with the S bit set should not get the editor as default tool, but IconX.

yes! that sounds right

[Steady]

I agree. That makes sense.

[AMIGASYSTEM]

Yes, but also the Def_project has in the Tooltypes the command "SYS:Tools/TexEdit" for the possible modification of the script, so here too the command "Installer" must be modified and inserted.

On OS 3.2 there is also a Def_Install, in my opinion the most appropriate one for installation script, but in the Icon Tooltype there is no Command, it is empty

[Kppot]

Originally Posted by AMIGASYSTEM

Speaking of OS 3.2, I've created a new OS4 style VisualPrefs+Birdie Skin with the gadgets style of the "PaperBlue" Skin plus the 3.2 Logo on the Title Bar.

Great efforts, is it compatible with 1200 or it requires RTG card?
Also, is there some sort of programs/tools list that needed to be installed so 3.2 would look like yours, I mean the toolbar, MUI popup windows etc please?

[AMIGASYSTEM]

You need an RTG system, everything works well even in PAL but the appearance is unpleasant, the skins used with Virtualprefs are in PNG of good quality, ditto for WBDock, see screenshot:

[FOL]

Originally Posted by AMIGASYSTEM

You need an RTG system, everything works well even in PAL but the appearance is unpleasant, the skins used with Virtualprefs are in PNG of good quality, ditto for WBDock, see screenshot:

My workbench looks much better than that (on my CD32) using standard hardware (with just 8MB Fast RAM). The backdrop and dock look ugly in your pic. Is it using differing.

[AMIGASYSTEM]

How many Colors do your backgrounds have ?

To get a good look at my wallpapers check out the screenshot posted above !

[FOL]

Originally Posted by AMIGASYSTEM

How many Colors do your backgrounds have ?

To get a good look at my wallpapers check out the screenshot posted above !

Screenmode 256 Colours.
24 Bit Image.
Using non differed gif's.


It looks very decent, even when using png icons.

[AMIGASYSTEM]

Nice, but a grey image with black icons covers the defects, on a PAL screen try to use a 24Bit PNG colored background and DualPNG Icons as shown in my screenshote you will notice the difference.