#Diavolo help
11 messages in this thread
To anyone using Diavolo as a backup utility…
I just got my hands on it, liked what I saw, and got the registered version. I
am using it in conjunction with a 525 meg Python streaming tape system to
backup my 200 meg Quantum harddrive. The harddrive is housed in an A2000 with
a GVP Series II 030/33 mhz Combo accellerator/controller. Okay, enough of the
stats…
I am having intermittent success in the backing up process. Sometimes it goes
through the whole process of backup and compare without a hitch. And it will
restore just fine. But MOST of the time it will just stop in the middle of a
backup or a compare, purely at random, at different places. There is something
going on that is tying it up. I can choose to abort the backup or compare, and
I get a requester asking me to confirm the action. If I select yes, then
another requester pops up saying it is clearing sub-processes and to please
wait. And there it stays. If I move the requester around with my mouse, it
erases the screen behind it. In other words, it won't refresh. If I go to a
CLI and type in a DOS command, the prompt drops down to the next line but the
command is not processed. If I try to launch a program from my menu, it does
not engage. Eventually, I can make it really lock up, and I have to reboot.
I have read the manual and tried various settings of the data transfer buffer,
changing it from the default 32 k to 128 k. I've fiddled with global buffer
settings, changing them from the default 800 k to 1000 k to Maximum Available.
But I really don't know what I'm doing. Oh, the shame!
Thanks,
Sean Hannon
Ad Rats – Stamford, CT
Hi…
maybe there is an old library version in your LIB: directory ???
greetings
Roland
greetings
Roland
Sean-
Some other important stats are-
What OS are you using? Have you tried running Diavolo without any WBStartup
and without any User-startup? There may be something interfering with Diavolo.
Another thing you should try is to get SCRAMmer from the libs here and see what
battmem bits are set and what other SCSI things are going on.
Did Diavolo successfully get the drive's defaults from the drive?
Mr. Zombie – now 76375,1776
Sean,
You need a line in your user-startup sequence that goes "GvpSCSICtrl (I.D.
#) dcoff". Mine reads "GvpSCSICtrl 4 dcoff". This line will take care of your
problem.
Regards,
Norman Austin 70743,1535
I was having problems with my backups using AmiBack and I would get a
criptic "SCSI Phase" error. I thought the problem might be with the program so
I downloaded Diavolo to test it out. Diavolo stopped working in the middle of
a backup with no error message. Perhaps something like this is happening to
you? My problem was a tape drive that didn't like some sizes of tapes.
Leslie –
> I would get a criptic "SCSI Phase" error. I thought the problem might be
> with the program so I downloaded Diavolo to test it out. Diavolo stopped
> working in the middle of a backup with no error message.
This sounds a lot like SCSI termination problems.
jsaklad@welchlink.welch.jhu.edu . . JimDoc, on AutoPilot
-> This sounds a lot like SCSI termination problems.
Nope. I double checked all terminations. For some reason my tape drive
will ONLY work with 250MB tapes.
Leslie,
According to many tape drive manufacturers, trying to mix 150 and 250
Meg cartridges in the same tape drive can cause problems using the lower
density tapes. In particular, read/write errors. The claim is that this is
due to different head wear patterns.
Don
-> trying to mix 150 and 250 Meg cartridges in the same tape drive can cause
problems using the lower density tapes.
I heard about that a little too late. It seems strange that a tape drive is
made to use smaller tapes but screws up if you take advantage of it.
Leslie,
Apparently the wear patterns are different. Since the DC6250 tapes are
physically thinner (the tape itself…not the cartridge) in order to allow the
larger capacity…they wrap slightly differently over the head and cause
different wear patterns.
Don
Leslie
re:
> trying to mix 150 and 250 Meg cartridges
It is true, and the reason 150mb should not be run with 250mb in the same
drive is that the 250mb tape is thinner. I forget the number of mils but
it causes them to track on the head differently and wear it differently.
On a brand new head they both work fine together, but older drives won't.
Tom
alternate: jonest@hfsi.com
I never met a man I didn't like…Will Rogers