I had exactl;y the same settings, I don't know what you picture did but all of a sudden it has started to work and I changed nothing.

Only difference was I was looking at tooltypes for things in WBStarup to see if there could be any clashes.

If it's not in the release then no.

Well whatever the problem is (In my icon set all icons have a drawer associated with them and it still doesn't work all the time) having a file/directory shouldn't be an issue and should be corrected in a future update/release, as it would only confuse new users. There's no technical reason as to why it has to be that way, the icon graphics is associated with the info file, not the directory/file.

Also the workbench windows seem to cache data in some way, you can manipulate the icons even though they don't exists in the file system. OS4 needs a better notification system so that file windows can update their content when stuff happens in the file system.

I followed what you detailed in your previous posts, howver, I still get the same results as Michael. Destination blank when it should point to ram:

As for the icons refusing to copy by using drag&drop I see you have already run into that problem. The weird thing is that it seems you can do it one minute and the next you can't from the very same icon you just made. I made a whole icon set yesterday and it happened randomly. Especially often when trying to copy stuff into the def icons in anvarc/sys.

it worked with upd4 the way i expected it to work. but now no longer.
(was online - will be again later this evening - just ping me then)

did both - but same result here. unarc only works in that way when started directly. started by clickin on a archive does just open unarc. without a destination path and without uarchiving the files...

Problem: Moving windows is slower.

Problem: PPaint opens a requester saying 'Attention: Memory Save Mode'

Solution: Edit your Startup-Sequence, the setpatch line should look like this: C:SetPatch ADDCHIPRAM 2 QUIET


Problem: Working with PPaint in low resolutions (320x240/320x256) and few colors (anything less than 256) doesn't work, as the BG color is always set wrong, it's purple when it should be black.

Solution: None


Problem: When working with low resolutions in PPaint and zoom mode, the pixel you are drawing with moves around a little depending on where you point at the screen, it's not in the center of the marker as it should be.
Solution: It's a little bit better if you set mouse speed to 1:1, but the active area of the pointer is still offseted to the right.

Solution: None

Problem: Not a bug, but the file requesters in ibrowse have black background, can that be changed? it looks so 1986 dos when they are black.

Problem: I have set destination to ram: in the unarc icon, but when i double click any archive it doesn't fetch the tooltype. however when i double click the unarc icon it fetches the tooltype.

Why would you want to do that?

Did you use the Update4 version of MediaToolBox to install the PPC native SmartFileSystem into the RDB?

Anyway, the only reason that doesn't fail with AmigaOS4 final is that the same version of SFS was loaded as kickstart module already, file systems are only loaded from the RDB if there is none with the same dos type already, or the one which is there already has a smaller version.revisions - which is the case with Update4 => you can't boot.

PPC native file systems must not be stored into the RDB with MediaToolBox, that's not supported and never will be, only m68k file system can be stored in the RDB!

Sorry, I don't understand what you mean with new SFS installed on the disk.

Did you use the Update4 kickstart modules except for SmartFileSystem and used the one included in the final version instead? That should have worked.

You can't boot the AmigaOS4 final Workbench partition with the Update4 kickstart modules, it's not SFS but a lot of programs and libraries requiring the newer exec, newlib, intuition, etc., with the Update4 kickstart modules you have to boot an Update4 Workbench partition.

what about this line?

(CHIPTYPE=ATIRadeon.chip)

try removing the '(' and ')' symbols

I will re-install it, do a few tests and report the results soonish.

Would someone who has a working "fast" Update4 installation AND a working "slow" Final installation do this for me:

1) Boot the Update4 installation, run Prefs/ScreenMode and write down the Mode Properties (Visible size, Maximum colours, Horizontal and Vertical freequencies).
2) Boot the Final installation and write down the same numbers.

See if there is any difference between the two installations and report back here.

[edit]
I've tried Update4, current beta system and Final release and I can't see any difference between them as long as the GUI settings are the same in each one.
Of course, if you have window drag-with-contents set in Final but not in Update4, then it will be slower.
[/edit]

ikir wrote:
Have you tweaked tooltypes of your monitor?

Edit your startup-sequence, add "ADDCHIPRAM=2" to setpatch to add 2 mb of emulated chipram and get ppaint working.

try using the new mode tooltypes instead of the old p96 steeings file

Quote:

I have a RADEON 9000 card, with the following monitor settings:
BOARDTYPE=Radeon
CMPLENGTH=6
(CHIPTYPE=ATIRadeon.chip)
(BORDERBLANK=Yes)
(BIGSPRITE=Yes)
SOFTSPRITE=No
IGNOREMASK=Yes
(DISPLAYCHAIN=Yes)
FAKENATIVEMODES=No
INTERRUPT=Yes
VSYNCMIN=60
VSYNCMAX=85
HSYNCMIN=31500
HSYNCMAX=64000
SETTINGSFILE=ENVARC:Sys/P96.prefs


atm your mixing BOTH systems together:

VSYNCMIN=60
VSYNCMAX=85
HSYNCMIN=31500
HSYNCMAX=64000

are the new system

SETTINGSFILE=ENVARC:Sys/P96.prefs

is the old system

oh no!
I use PPaint every day!
I get a requester saying 'Attention Memory Save Mode'
when i start it now. :/

And yes, window moving is slower here too.

Maybe the "Avoid flicker"-Switch in the GUI prefs?