#I/O problem in 2.0!
16 messages in this thread
Its *not* misaligned drives!
It has to do with files being saved from within a program and copied from
the shell. I *know* it sounds unlikely but try this:
Under 2.0 Get into AmigaVision, create a small script and save it to a
floppy.
Under 1.3 Then try to use the shell copy command in 1.3 to copy the file.
You *will* get a read error.
I also duplicated this on another Amiga 3000.
Trust me, I know enough to know when I have a problem with a disk drive.
There is a bug here.
-mark=
For what it's worth: I've had CedPro create a couple of "interesting"
files under the release version of 2.0. By interesting, I mean they appear
in the directory listing, but can not be accessed by any command. At one
point, I had 3 startup-sequence files in my S: directory! DiskSalv (which
runs great on the 3000) can get them back.
Methinks there are a few bugs in there…
– Dave
Try making files with deluxe paint, under 2.0 and then accessing them
under 1.3. I can only get weird behavior when I save directly to the
floppy disk.
-mark=
Mark,
I don't have AmigaVision yet, so I couldn't exactly duplicate the problem
you've found. I've successfully done the following:
1. On the 3000, under 2.0, call up a text file in Ed
2. Save the text file to a floppy in DF0: on the 3000 (the floppy
had been formatted under 1.3 on a 2000)
3. Put the floppy in the 2000, COPY the text file to another directory
No problem here. No problem swapping back and forth all manner of
files.
Rich
Try that with Deluxe Paint. It may have to do with different ways of
writing files. Text files and binary files are different.
-mark=
Mark, I beg to differ… all files are written the same way in the end, I
guess. And there isn't a difference between a text file and a binary file,
since the system has no idea that a text file is a text file.
Khalid.
There are two problems here: 1) If you wrre beta testing 2.0 we were
serious about backing up with a non-image backup program, reformatting,
then restoring.
Several times a filesystem bug that would create multiple copies of a fine
under the same name surfaced in beta. We believe the release version is
free of this problem, but you may have a time bomb waiting to surface.
Note: also make sure that any filesystem you've loaded into a hard drives
rigid disk block is the latest one. (Its located on the A3000 Install
disk). If you use an older one you are inviting the same beta problems to
visit you again.
2) There is a bug when writing to OFS floppies that shows up with programs
that seek on empty files. The sequence numbers within in the OFS file
blocks get out of step, and the file is not readable under 1.3. (But is
still readable under 2.0) The work around for now is to COPY those files
under 2.0.
Yes, there will be subsequent releases of 2.0 in the future with this (and
other) bugs fixed.
andy
Thank you Andy!
I feel vindicated!!!
-mark=
Glad to help.
(you won't forget my fee, of course 🙂 Only kidding!)
andy
Andy,
Well, that ends _that_ little controversy.
Rich
Guys,
I'll take a wild shot at this, since Mark mentioned to try this in DPaint.
Something to do with DMA access as the computer is writing to the floppy.
Can this be it?
Anyways, that is my 2 cents, I'm outta here.
Mike…
Mark,
To my knowledge, neither DeluxePaint III nor AmigaVision "officially" run
under 2.0. As a matter of fact, CBM did not ship AV with my A3000 because
"It isn't ready yet". My guess is that both products are trying to use the
old dos.library and they are getting some flakey results from the new
library. My wife called about DPIII and the folks there told her that they
would not be releasing DPIII for 2.0 until the OS was in ROM.
Chris -)—–
Time to get ahold of EA and bang their heads together. Maybe a version
supporting 2.0 might be able to wait for it to get into ROMs… but Deluxe
paint is too major a tool for too many for them to let it stay incompatible
with 2.0… I can live with it's crappy file requester, but I had it lock
up on me on an A3000… and I don't think that a $100 (or so) program
should be allowed to influence my purchase of an A3000 or adpotion of 2.0!
–Eet–
Director of Mayhem
Extra Terrestrial Imports, Ltd.
Yeah, I agree. I have had a few problems also, but the most annoying is
lockup when using the fill tool. this happens more than 50% of the time.
If I avoid it then I'm usually fine. and if I remember right, it isonly a
problem when filling the whole screen…
Perhaps neither work officially under 2.0, but they both do work. I
haven't noticed any problems with AmigaVision yet (a FABULOUS program!).
DPIII seems to work, but I've been told that overscan does wierd things
with it.
BTW, AV doesn't use all the different fonts you can choose, and it also
looks slightly off under 2.0, drag bars being a pixel or two too high and
all.
— Ethan
Ethan —
Still, AmigaVision is not "promised" to work under 2.0. That may forgive
(if not explain) the problems that were reported.
Chris -)—–