Well, I'm using AmigaForever for quite a while now, but never experienced something like this:

Newly the emulated Amiga (OS 3.9 + BB1 + 2) claims that "System:" is write protected. A brief survey with DOpus revealed that "System:" and "Work:" had the "Archive"-bit set.
So I removed the checkmarks for "Archive" with DOpus and restarted AF - just to get the message "System:" being write protected again.

Another check with DOpus - the "Arcive"-bit is back again!
How's that possible?

"O.K...", I thought, "perhaps I should better change the protection bits on the Windows (XP) side.".

No sooner said than done:
I opened WinExplorer, highlighted C:\Documents and Settings\All Users\Documents\Amiga Files\System\dir\System and \Work, pressed the right mouse button, clicked on "Properties", removed the checkmark at "Attribute: write protected", clicked on "Advanced" and removed the checkmark from "Folder can be archived" as well, clicked on "Accept" and finally on "O.K.".

And - what can I say - the folders "System" and "Work" are still write protected. I e.g. cannot save changed prefs settings. Sh*t!

I tried all I could think of to get the write protection removed (played around e.g. with "Authorisations" and "Sharings") - but in vain. With constant diabolicalness the system refuses to remove the write protection.

I never experienced something similar before (and yes, I have full admin rights on my PC)...

Does someone here have an idea what could be going wrong there?

_________________
Ciao

Dandy
__________________________________________
If someone enjoys marching to military music, then I already despise him.
He got his brain accidently - the bone marrow in his back would have been sufficient for him!
(Albert Einstein)

@Dandy

Problem solved - I had not noticed the "Read/Write" checkbox in AF's HD config section - and therefore didn't set the checkmark, of course...

I think I have to see my oculist...

Last edited by Dandy on 28-Jun-2012 at 11:52 AM.

_________________
Ciao

Dandy
__________________________________________
If someone enjoys marching to military music, then I already despise him.
He got his brain accidently - the bone marrow in his back would have been sufficient for him!
(Albert Einstein)

@Dandy

Does this affects OS1.3 version as well?
I experienced the same problem when trying to tinker with AmigaBasic on older Amiga setups (like 1.3).

Cheers
g0blin

_________________
Now running AmigaOS4.1.6 on Sam440-flex @800MHz.
also running: Linux Debian 5 and Linux Kubuntu 12.04.
AmigaForever2013 user.
"iBatch" and "Boing Attitude" translation team.
Amiga Translator's Organization.

@g0blin

Quote:

g0blin wrote: @Dandy Does this affects OS1.3 version as well? I experienced the same problem when trying to tinker with AmigaBasic on older Amiga setups (like 1.3). Cheers g0blin

Pheeew - OS 1.3?
Oh mate, THATs long ago!
I haven't used 1.3 since ages - so I cannot tell you.

But basically I'd guess that if a device with OS 3.1 (or 3.9 like in the case at hand) is write protected from the AmigaForever config, it also will be write protected with OS 1.3.

BTW - has it been called "OS 1.3" or was it rather "Workbench 1.3"?

Last edited by Dandy on 02-Jul-2012 at 05:41 AM.

_________________
Ciao

Dandy
__________________________________________
If someone enjoys marching to military music, then I already despise him.
He got his brain accidently - the bone marrow in his back would have been sufficient for him!
(Albert Einstein)