#QB 5.0 more bugs?
11 messages in this thread
? I just got QB 5.0 and patched it to 5.1. I have run into a couple of
problems. (not mentioned so far).
My system is A3000 with 2 drives and an Archive Python (DAT)
1) No matter what I set the buffer options memory type to be
QB always uses GRAPHICS RAM (I can see the ram use from WB).
2) I have tried the Multiple backup macro and no the QB always
puts up the backup target requestor for each volume. I have
manually set the requestor to OFF and also your macro seems
to do a DisplayOptionsOff. If I do the backup by hand the
system will NOT display the requestor.
3) This is not really a problem, but a request. There should be
a function to retrieve the backup set names from a tape volume
so we don't have to write down each backup we have made to a tape
(this is especially a pain with a 2 Gig tape and 100 or so backup
sets to the single tape)
Hope you can help me out…
Jeff
Jeff,
1) This is a Commodore problem. To ensure that we are getting memory that
we can DMA to and from, we have to set the 24BITDMA flag when asking
for memory from the system. On A2000's and A500's with normal
autoconfig
memory, then it just allocate whatever type of memory is available since
it
is all 24BITDMA-able. On the A3000, however, the 24BITDMA flag causes
chip memory to be chosen for buffers if you only have 32 bit memory
installed. But, on the A3000, the scsi.device can DMA anywhere in the
system, but from a progamming standpoint, there is no way to know this.
The reason is that if you have an A2000 with an accelerator that puts
its
32 bit memory outside the normal autoconfig space, then scsi controllers
cannot DMA in that 32 bit RAM area. This is a real problem on the Amiga
and needs to be addressed by Commodore. They have been informed about
this
and I hope they will do something about it. What we need is a way to
ask
each scsi.device where it can DMA since it should know.
2) The macro has worked for me. It may have broken in 5.0.1, but I don't
see
how. I'll look into it.
3) You can space to each backup on a tape, then read the catalog and
choose
GetSessionInfo from the Utilities menu. In a later version, this
process
wil probably be automated through a macro.
Mark Thomas
Central Coast Software
A division of New Horizons Software, Inc.
Mark, having followed this thread I'm getting more and more worried about
using 5, even patched, once I eventually receive it. I've gotten the
impression that it doesn't properly handle restores of the older but recent
versions, etc.
Is there any list of known 5.01 problems that you can post?
Ron
Ron,
What problems are you referring to when you say that Quarterback 5.0 does
not restore QB 4.0 backup set? I looked back at this thread an didn't see
any mention of problems pertaining to restoring old backup set and I don't
know of a problem with this.
Mark Thomas
Central Coast Software
A division New Horizons Software, Inc.
One of the messages suggested a problem; perhaps on the user forum.
Personally I hope there aren't any.
I'm also worried about using compression. I backup to floppy but I hear
that your odds of restoring from a compressed backup set aren't good, that
the 'index' to the backup set doesn't know what floppy a file is on if you
use compression. Note that PC oriented products have been using
compression for years, so it would be nice to know that I could safely use
the new compression on QB.
Ron
Ron,
Currently we do have to scan through the whole backup when restoring
compressed files.
Other than this inconvenience, there are no problems.
Mark Thomas
Central Coast Software
A division of New Horizons Software, Inc.
Mark, while forgetting the other apparent non-issues, this one issue is
enough to make compression very dangerous, IMHO. If there is the slightest
problem with a single file, the whole backup could be rendered unusable, if
you never reach the file you wanted. I would have thought that the last
disc in the backup set would have had an index on it telling the program
where to find a given file. Note that products like Central Point Backup
not only do things like that, they also put that index on the hard drive
itself in a file. That way, if you're only restoring one file, it quickly
tells you what floppy to put in, and the restore is finished very, very
quickly.
I hope that New Horizons considers this problem serious enough to do
another patch quickly. As badly as I need to reduce the size of my backup
sets, I'm afraid to use this long overdue feature. I'm really surprised
that this could happen.
Ron
Ron,
Thanks for the concern. I'm sure that something will be done about the
compression restore scheme.
Mark Thomas
Central Coast Software
A division of New Horizons Software, Inc.
Excuse me, but scanning through 50+ disks to recover one file from the last
disk in the set, seems a major problem to me ! When will this be changed ?
– J0RGEN …..by Whap! from DENMARK
J0RGEN,
You do understand that this only occurs when using compression, right?
We're looking into the problem.
Mark Thomas
Central Coast Software
A division of New Horizons Software, Inc.