Vice 1.21 drive issues.

Started by Stephane Richard, May 17, 2007, 03:48 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Stephane Richard

Ok just wondering if it's me or what that's having this problem :-).

1. no overwriting of files.   I save a file as menu1 the add chances, dsave"menu1" and assuming it works I leave, come back to winvice start it up, reattach the disk image and dload "menu1 only to find it's the old version.

2. so naturally I thought I was smart here and did a dsave"menu2 this time around.  so I leave, come back, reattach the disk image but menu2 isn't there.  so um  any other vice 1.21 users out there have these same problems?  is there anything I should know about that helps avoid these things?

I'm using winvice 1.21 and my 8 drive is setup as a 1581.

This time, i'm gonna try with a classic 1541 disk image instead see what happens. then i'll try with a 1571 disk image ;-)
When God created light, so too was born, the first Shadow!

MystikShadows

nikoniko

Hmm.. I'll have to give it a try. I usually have VICE save to folder rather than disk image, and that still seems to work fine in 1.21.

nikoniko

Just tested it out with a .d64 and a .d81, and both work for me. Changes persist after leaving VICE and starting it again. Save with replace works, too. The only thing I can think of, make sure that when you attach the image, you don't have "Attach read only" checked off by mistake.

EDIT: One more thing: make sure that when you have a .d81 inserted, you switch the drive mode to 1581 as well. Otherwise when you try to save, it will fail and you'll get a flashing drive light in the lower right of your window. If you're in a hurry to exit, it could be easy to miss since BASIC itself doesn't warn you that it failed.

EDIT2: Oops. I see you already said that you have your drive set as 1581.

Stephane Richard

Yeah my settings are defaulted to a d81 for unit 8.  it's weird, I'm not sure why it does that.  but so far it's been pretty regularly not allowing me to overwrite (unless theere's a setting somewhere that i'm not thinking about.

now, how do I set it to write to a folder instead?  I didn't see anything for that in the drive settings?  doing that might save me alot of time.
When God created light, so too was born, the first Shadow!

MystikShadows

nikoniko

Just don't attach a disk, or detach any disk which is already attached, and turn off True Drive Emulation. Now when you access any files, they'll write to the last Windows folder you accessed with WinVICE.

I only use disk images when absolutely necessary. When writing to folder, you have the advantage of not having to worry about running out of space (unless your HD is full) or swapping disks.

Stephane Richard

Ahhhhhhhhhhhhhhhhhhhhhhh...that's starting to make sense now ;-)....I take it you transfer to dXX when you aim to copy things on a real system ;-)

Thankyou.  I think I can start having fun again ;-)....hehe
When God created light, so too was born, the first Shadow!

MystikShadows

Stephane Richard

well, looks like I'm back to square one.

It effectively does what you say it now writes to folder as expected...but i'm faced with the same situations I decribed above...it won't over write a file still which means it doesn't save my changes..
first save is called "filename".P00  second save is .P01, third save is P02

but when I "dload" something it always tries to get the P00 which is the first version of a file.  hence it gives me, after loading the file, that no changes were saved where in reality it's in P02.  Ps there a setting that I need to tell it to always overwrite the filename?  or perhaps a setting to tell it to get the last PNN file in the list of files of the same name?
When God created light, so too was born, the first Shadow!

MystikShadows

nikoniko

Ah, sorry. I forgot there's an .INI setting I changed ages ago to stop the behavior you describe.

In VICE.INI, look for these lines:

FSDevice8SaveP00=1
FSDevice9SaveP00=1
FSDevice10SaveP00=1
FSDevice11SaveP00=0

By default, VICE creates .Pnn files when you save to devices 8, 9 or 10, and raw CBM files when saving to device 11. If you want another drive to save raw files, change the setting to 0. Or just use device 11 for saving. What I do is have all the settings switched (0,0,0,1), so that if I need to export a file that's compatible with other emulators, I can use device 11.

The only things to keep in mind are the compatibility issue, and that if you ever use the DOS version of VICE, I think you're limited to filenames of no more than 11 (8.3) characters.

Stephane Richard

When God created light, so too was born, the first Shadow!

MystikShadows