English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 03 November 2009, 20:43   #1
GIB
Registered User
 
Join Date: Oct 2009
Location: Gibraltar
Posts: 10
Disk Write Protected

Amiga Forever is installed on my HD, when i try to save a program i wrote in AmigaBasic then a message pops up telling me " DISK WRITE PROTECT "
How is this possible ? i am using my HD and donĀ“t have any othere disk drives attached to my laptop . Can some 1 explaning how to save programs pls ?
Thanks
GIB
GIB is offline  
Old 03 November 2009, 20:50   #2
TCD
HOL/FTP busy bee
 
TCD's Avatar
 
Join Date: Sep 2006
Location: Germany
Age: 46
Posts: 31,530
Inside WinUAE press F12, go to the hard drives panel, click on the first one and on 'Properties'. Make sure the the 'Read/write' box is checked. Do that for any other HD aswell. Now save the config (don't know how AF handles it, but it should work).
TCD is offline  
Old 03 November 2009, 23:06   #3
GIB
Registered User
 
Join Date: Oct 2009
Location: Gibraltar
Posts: 10
write protect

Quote:
Originally Posted by TheCyberDruid View Post
Inside WinUAE press F12, go to the hard drives panel, click on the first one and on 'Properties'. Make sure the the 'Read/write' box is checked. Do that for any other HD aswell. Now save the config (don't know how AF handles it, but it should work).

Hi, after ur advise, it is still the same. "Volume workbench write protect" Dunno what els i can do for i am not familiar with all this WINUAE thing. it is to technical for me. all i try to do is to use the amigabasic and beeing able to save it.
Thanks for ur answer.
GIB.
GIB is offline  
Old 03 November 2009, 23:13   #4
TCD
HOL/FTP busy bee
 
TCD's Avatar
 
Join Date: Sep 2006
Location: Germany
Age: 46
Posts: 31,530
Okay, hope someone who owns AF can help you with it. Fingers crossed
TCD is offline  
Old 22 November 2009, 07:40   #5
mcb
Registered User
 
mcb's Avatar
 
Join Date: Oct 2008
Location: - / -
Posts: 47
I believe that you were sent an email with a reply to this question on November 8. You may want to check your spam folder.

Unlike the 3.X environment, the 1.3 system hardfile used to boot many games and the Workbench 1.3 environment is write protected by default to prevent corruption, as this particular system is generally used for gaming, not for productivity.

In a future version of Amiga Forever there may be an option for this. So far, yours was the first case where having this partition protected turned out to be an annoyance, whereas in the past it was more easily damaged and now this isn't the case any longer.

The read/write status can be modified manually, for example by using Notepad to edit the applications.xadml configuration file.

You described that you have Windows Vista, so applications.xadml should be in:

C:\ProgramData\Cloanto\RetroPlatform\Amiga Forever\Catalog

Right at the top of the applications.xadml you will see the section for <title>Workbench 1.3</title>.

Go to line 25, and edit it as follows:

<boot type="hdf" readonly="true">135</boot>
->
<boot type="hdf">135</boot>

Save the file, and refresh the content of the Applications tab, if open (press F5). From now on the Workbench 1.3 boot partition will not be write-protected.
mcb is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
harddisk write protected!? jitrnic support.WinUAE 3 24 January 2010 19:02
Can't Untick Write-Protected Neji support.WinUAE 22 29 August 2009 07:15
Disk is write protected ? THX1138 support.Apps 10 01 December 2002 10:09
Write protected? Geordy New to Emulation or Amiga scene 8 30 October 2001 17:15

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 17:52.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.33038 seconds with 13 queries