NOT DOS DISK ???

[browny]

Hi Folks !,
Anyone got any ideas as to why MakeCD is trashing
my system partition?.
Explaination:
When i use Makecd `on the fly` i have no probs.
Then when I start to use an image file and copy to disk,that part of the process is ok, But after doing that and turning the miggy off, when i turn the miggy back on the dreadded `NOT A DOS DISK ` appears.
This is always after i have been using MakeCD
to create image files.
I am getting sick of reformatting and installing the system back to normal.
I am using a ELBOX 4 way IDE I/face, which has my HD and CD writer attached, and am running them with IDEfix97 S/Ware.
Thanks in advance!
Browny

[vortexau]

° This is just an idea, but is it possible to "Write Protect" the Sys Partition?
Another idea- Virus Check!

[xeron]

Yes. "Lock SYS: On" will write protect your system partition.

[browny]

Thanks for the idea`s Vortexau,
I take it that you mean ticking the option for READ ONLY in the icon prefs? .
I will try that.
Can any one point me in the right direction for a
Bug Bustin` Virus checker.
Cheers

QUICK EDIT !! @ Tickly Where do i find `LOC SYSTEM`?
,in HD Toolbox?
I know your there Blobby!!

If there is a God he did all on an A1200 !!.  :-P

[xeron]

its a standard AmigaOS CLI command.

"Lock SYS: On" to lock your system partition, "Lock SYS: Off" to unlock it.

[browny]

Thanks Tickly,
I`m no programmer but can i add that line to my start up sequence and the jobs done?
Thanks Again

[xeron]

Well you could, but it might not be a good idea to have it permanently locked.

I just use lock whenever i'm running something i don't entirely trust for whatever reason, and unlock it again after.

[browny]

Thanks again tickly,
This thing has been bugging me for age`s, hopefully i can resign it to the out tray!.

ATB Browny


@ Kronos,Interests: Blinding the enlightened .
Could not resist it !

[Piru]

Yes. "Lock SYS: On" will write protect your system partition.

I'm afraid this does not help at all. Lock use filesystem level write protection, that is, it does not protect for exec device driver level writes. The only way disk can get NDOS is by direct writes via device driver, normal filesystem operations don't trash the disk.

Make sure the MakeCD settings are not set to hold the image file on block device located on >4gig area (global settings/Further settings/Other settings/Block medium). I'm not sure but I'd imagine MakeCD can't handle >4gig areas.

[browny]

Cheers Piru,
I have checked the Block medium and all is ok, i think your on to something with the >4gig area though.
My HD is bigger than that.
Also on the same page is Permit Exall() and Unprotect,  both these settings are enabled, what would you suggest?

[Piru]

browny:

Check that all filesystems used handle >4gig properly (that is, they have either NewStyleDevice (NSD), TrackDisk64 (TD64) or DirectScsi (DS) support. Remember that having the correct file in L: is not enough, you need to check that RDB has the correct filesystem(s) aswell.

Permit ExAll() and Unprotect are not necessarily needed, but can be enabled for FFS V44/V45, SFS and PFS3.

[browny]

Thanks again Piru,
I checked the RDB,all is well.
Then I looked in L: for the FFS, would you believe it
it was not there!.
for some reason when reinstalling WB it was not throwing FFS into L:
God knows how that happened, but hey I knew the answer was here.

Thanks to all
May all your code be bug free!!