Drive Image 2002 Slower transfer rates
George Pertoli
when making and image are dramatically different. My older computer
is actually faster than my newer one. How can this be? Here are the
spec's for both computers.
P3 450 slot one
768 mb ram
12 gig (5400) primary drive
40 gig (7200) slave
windows xp (not that it matters, i think)
transfer rate is 359mb per minute.
the other computer is...
amd xp1600
epox mobo (via chipset)
ibm deskstar (7200) 20 gig primary
ibm deskstar (7200) 40 gig slave
512 ram
transfer rate 195mb per minute!
this is a transfer that is set up in windows and reboots the computer
(in both computers) to caldera dos. I've done a bit of research and
have seen some fixes that entail altering a file on the floppy rescue
disks, but I never use those disks and was wondering if someone knew
what was happening here, and has an alternate fix. Actually any help
would be greatly appreciated.
George
Rod Speed
George Pertoli <Georg...@excite.com> wrote in message
news:9fd7cvo256215mp4s...@4ax.com...
> I have two computers running Drive Image 2002. The transfer
> Speeds when making and image are dramatically different. My
> older computer is actually faster than my newer one. How can this be?
Its always been a real problem with DI, that big variation in the thruput.
Try the /IDE=yes command line switch on the
slow PC, that can make a hell of a difference.
Make sure that DMA is enabled on both systems.
> Here are the spec's for both computers.
> P3 450 slot one
> 768 mb ram
> 12 gig (5400) primary drive
> 40 gig (7200) slave
> windows xp (not that it matters, i think)
> transfer rate is 359mb per minute.
> the other computer is...
> amd xp1600
> epox mobo (via chipset)
> ibm deskstar (7200) 20 gig primary
> ibm deskstar (7200) 40 gig slave
> 512 ram
> transfer rate 195mb per minute!
> this is a transfer that is set up in windows and reboots the computer
> (in both computers) to caldera dos. I've done a bit of research and
> have seen some fixes that entail altering a file on the floppy rescue
> disks, but I never use those disks and was wondering if someone
> knew what was happening here, and has an alternate fix.
I'd try the floppy approach just to see if it fixes the problem.
It isnt hard to edit the virtual floppy so that it works with the
way you use it if it does fix the problem, its just easier to
test using the floppys because its easier to edit the command
line to add that /IDE=yes switch to see if it helps.
George Pertoli
wrote:
>
>George Pertoli <Georg...@excite.com> wrote in message
>news:9fd7cvo256215mp4s...@4ax.com...
>
>> I have two computers running Drive Image 2002. The transfer
>> Speeds when making and image are dramatically different. My
>> older computer is actually faster than my newer one. How can this be?
>
>Its always been a real problem with DI, that big variation in the thruput.
>
>Try the /IDE=yes command line switch on the
>slow PC, that can make a hell of a difference.
Woooooooooooooooooooooohooooooooooooooooooooooooooooo
1259mb per minute ......!!!! ;-)
Thanks for pushing me to try that Rod !!!
Now is there anyway to make that adjustment on the windows version ?
So when it reboots from windows to run, it does the same thing.
Thanks again.
GP
Rod Speed
>>> I have two computers running Drive Image 2002. The transfer
>>> Speeds when making and image are dramatically different. My
>>> older computer is actually faster than my newer one. How can this be?
>> Its always been a real problem with DI, that big variation in the thruput.
>> Try the /IDE=yes command line switch on the
>> slow PC, that can make a hell of a difference.
> Woooooooooooooooooooooohooooooooooooooooooooooooooooo
> 1259mb per minute ......!!!! ;-)
> Thanks for pushing me to try that Rod !!!
> Now is there anyway to make that adjustment on the windows version ?
> So when it reboots from windows to run, it does the same thing.
Yeah, just edit the virtual floppy. The manual spells out how to
do that pretty clearly. You're really just editing that command
line in that virtual floppy in exactly the same way you did it with
a real floppy. You just have to open the virtual floppy to do that.
> Thanks again.
No problem, hope you superglued your sox on |-)
Roger Dejus
Thanks.
Bob Horvath
<Georg...@excite.com> wrote:
You are kidding about that speed, aren't you. Did you mean 259 per
minute.?
Rod Speed
Roger Dejus <de...@aps.anl.gov> wrote in
message news:3EC43956...@aps.anl.gov...
> Is the /IDE switch available for DriveImage 5.0?
Yep.
> Browsed docs and PowerQuest site but could not find anything!
Yeah, its never been that well documented for some reason.
> Rod Speed wrote:
>> George Pertoli <Georg...@excite.com> wrote
>>> I have two computers running Drive Image 2002. The transfer
George Pertoli
<bhorv...@comcast.net> wrote:
>On Thu, 15 May 2003 21:53:35 GMT, George Pertoli
><Georg...@excite.com> wrote:
>
>You are kidding about that speed, aren't you. Did you mean 259 per
>minute.?
>
No I'm not. It imaged 3 gigs in under 3 minutes. No Joke
1259 mb per minute
George Pertoli
wrote:
>
>George Pertoli <Georg...@excite.com> wrote in message
>news:rt28cv8e676m4ovse...@4ax.com...
>> Rod Speed <rod_...@yahoo.com> wrote
>>> George Pertoli <Georg...@excite.com> wrote
>
>>>> I have two computers running Drive Image 2002. The transfer
>>>> Speeds when making and image are dramatically different. My
>>>> older computer is actually faster than my newer one. How can this be?
>
>>> Its always been a real problem with DI, that big variation in the thruput.
>
>>> Try the /IDE=yes command line switch on the
>>> slow PC, that can make a hell of a difference.
>
>> Woooooooooooooooooooooohooooooooooooooooooooooooooooo
>
>> 1259mb per minute ......!!!! ;-)
>
>> Thanks for pushing me to try that Rod !!!
>
>> Now is there anyway to make that adjustment on the windows version ?
>> So when it reboots from windows to run, it does the same thing.
>
>Yeah, just edit the virtual floppy. The manual spells out how to
>do that pretty clearly. You're really just editing that command
>line in that virtual floppy in exactly the same way you did it with
>a real floppy. You just have to open the virtual floppy to do that.
It doesn't work. Something resets the line on reboot. It just goes
back to the orignal command line minus my change ;-(
George
Rod Speed
"George Pertoli" <Georg...@excite.com> wrote in message news:esn8cvs2nffce83vr...@4ax.com...
> On Fri, 16 May 2003 08:12:23 +1000, "Rod Speed" <rod_...@yahoo.com>
> wrote:
>
> >
> >George Pertoli <Georg...@excite.com> wrote in message
> >news:rt28cv8e676m4ovse...@4ax.com...
> >> Rod Speed <rod_...@yahoo.com> wrote
> >>> George Pertoli <Georg...@excite.com> wrote
> >
> >>>> I have two computers running Drive Image 2002. The transfer
> >>>> Speeds when making and image are dramatically different. My
> >>>> older computer is actually faster than my newer one. How can this be?
> >
> >>> Its always been a real problem with DI, that big variation in the thruput.
> >
> >>> Try the /IDE=yes command line switch on the
> >>> slow PC, that can make a hell of a difference.
> >
> >> Woooooooooooooooooooooohooooooooooooooooooooooooooooo
> >
> >> 1259mb per minute ......!!!! ;-)
> >
> >> Thanks for pushing me to try that Rod !!!
> >
> >> Now is there anyway to make that adjustment on the windows version ?
> >> So when it reboots from windows to run, it does the same thing.
> >
> >Yeah, just edit the virtual floppy. The manual spells out how to
> >do that pretty clearly. You're really just editing that command
> >line in that virtual floppy in exactly the same way you did it with
> >a real floppy. You just have to open the virtual floppy to do that.
> It doesn't work. Something resets the line on reboot. It just
> goes back to the orignal command line minus my change ;-(
Then you arent editing the virtual floppy properly. You sure
you're actually saving the changes you make to the virtual floppy ?
Try editing the virtual floppy to add that command switch.
Reboot and check the virtual floppy again. Bet you find that
you didnt actually save the change you made to the virtual floppy.
Rod Speed
"George Pertoli" <Georg...@excite.com> wrote in message news:mon8cv0u0cg8gg79a...@4ax.com...
Yeah, plenty get thruput over 1G
George Pertoli
wrote:
are we talking about the file located here
C:\Program Files\PowerQuest\Drive Image 2002\VFD
PQVF.VFD.....this file There is a DEFAULT.VFD as well
I open it with notepad (this takes some time)
and find this section.....
@ECHO OFF
PROMPT $P$G
REM -------------------------------------------------------
REM -- Put keyboard codes (xx) and --
REM -- code page variables (yyy) here. --
REM -------------------------------------------------------
REM MODE CON CP PREP=((yyy) EGA.CPI)
REM MODE CON CP SEL=yyy
REM KEYB xx,yyy
REM -------------------------------------------------------
REM -- Put network or CD-ROM drivers here. --
REM -------------------------------------------------------
REM Windows DOS:
REM MSCDEX.EXE /D:driver_name [/L:drive_letter] [/M:buffers]
REM Caldera DOS:
REM NWCDEX.EXE /D:driver_name [/L:drive_letter] [/M:buffers]
MOUSE
SET TZ=EST5EST
ECHO Drive Image 2002
ECHO Copyright 1994-2002, PowerQuest Corporation
ECHO All rights reserved.
ECHO
ECHO Loading. Please wait...
PQDI /CMD=QIMAGE_BACKUP /PWRDWN=0 /ide=ON changing
this line
REBOOT
I've closed it and reopened it to see the change has happened. Then I
run Drive Image 2002 and it runs at the slow speed. I stop it.
Reboot, and ck the file, only to see it's back to it's original state.
George
Rod Speed
"George Pertoli" <Georg...@excite.com> wrote in message news:iuq8cvkpesgks3nq7...@4ax.com...
You need to reboot the PC and see if the change has
stuck. Bet it hasnt. Because you arent saving it properly.
> Then I run Drive Image 2002 and it runs at the slow speed. I stop it.
> Reboot, and ck the file, only to see it's back to it's original state.
>
>
>
>
> >
> >
George Pertoli
wrote:
Rod,
It's there after reboot. What do you mean "Saving it properly"?
GP
Rod Speed
"George Pertoli" <Georg...@excite.com> wrote in message news:nps8cv459evmlthve...@4ax.com...
I was thinking that you likely werent saving it permanently
to the hard drive. That was the reason for the reboot.
Try
http://www.powerquest.com/support/primus/id2888.cfm
Paul Busby
> Roger Dejus <de...@aps.anl.gov> wrote in
> message news:3EC43956...@aps.anl.gov...
>
>> Is the /IDE switch available for DriveImage 5.0?
>
> Yep.
>
>> Browsed docs and PowerQuest site but could not find anything!
>
> Yeah, its never been that well documented for some reason.
I've just edited both files with DI5.01 & done an image. On My Asus
A7V266-E/XP1800+/512MB DDR, throughput has doubled to 699MB/min. Next
time Task Scheduler runs Quick Image, I'll check the throughput there as
well. So thanks for the tip Rod. This increase doesn't surprise me too
much 'cos my brother noted a 3 fold increase after changing his m/b
(without that switch).
Rod Speed
Paul Busby <m...@privacy.net> wrote in message
news:ba3m9d$ovs9o$1...@ID-173588.news.dfncis.de...
> Rod Speed wrote
>> Roger Dejus <de...@aps.anl.gov> wrote
>>> Is the /IDE switch available for DriveImage 5.0?
>> Yep.
>>> Browsed docs and PowerQuest site but could not find anything!
Forgot to say that the PowerQuest site is so bad
that I usually use google to find appropriate stuff
on it. There's quite a bit of quite good documentation
there, just too hard to find except by using google.
The site 'designers' should be taken out the back and shot.
>> Yeah, its never been that well documented for some reason.
> I've just edited both files with DI5.01 & done an image. On My Asus
> A7V266-E/XP1800+/512MB DDR, throughput has doubled to 699MB/min.
> Next time Task Scheduler runs Quick Image, I'll check the throughput
> there as well. So thanks for the tip Rod. This increase doesn't
> surprise me too much 'cos my brother noted a 3 fold increase
> after changing his m/b (without that switch).
Yeah, that problem has been around with DI for years now.
Bit of an inditement that they havent fixed it really.
Bob
<snip>
:Try the /IDE=yes command line switch on the
:slow PC, that can make a hell of a difference.
Thanks for the /IDE=yes tip, Rod...it made a huge difference on my
system.
What exactly does this switch do? I was unable to find anything about
it in the DI Help file as well as their website.
BDY
Rod Speed
Bob <am_...@panix.com> wrote in message
news:ba40td$1r4$1...@reader1.panix.com...
> Rod Speed <rod_...@yahoo.com> wrote:
>> Try the /IDE=yes command line switch on the
>> slow PC, that can make a hell of a difference.
> Thanks for the /IDE=yes tip, Rod...
> it made a huge difference on my system.
No probs, thats what these technical groups are all about.
> What exactly does this switch do?
Basically tells DI about how the hard drive can be used.
The basic stuff like UDMA4 etc reported elsewhere.
> I was unable to find anything about it in
> the DI Help file as well as their website.
Yeah, I cant find anything either, even when using google.
google isnt that great when looking for something like that tho.
Its a switch that powerquest can suggest
if you complain about lousy thruput.
Bob Horvath
wrote:
Do you really mean ide/yes or ide/on . I've seen "on" but never "yes"?
Bob
Rod Speed
Bob Horvath <bhorv...@comcast.net> wrote in message
news:kkbbcvciphf2dg1ds...@4ax.com...
> am_...@panix.com (Bob) wrote
> Do you really mean ide/yes or ide/on . I've seen "on" but never "yes"?
I meant /ide=yes
That obviously works.
Likely /ide=on does too, havent tried it.
Rod Speed
Bob Horvath <bhorv...@comcast.net> wrote in message
news:kkbbcvciphf2dg1ds...@4ax.com...
> am_...@panix.com (Bob) wrote
> Do you really mean ide/yes or ide/on . I've seen "on" but never "yes"?
I meant /ide=yes
That obviously works.
Looks like /ide=on is the best to use, and that does
turn up powerquest documentation using google.
And http://www.powerquest.com/support/primus/id1709.cfm says
/IDE=ON
--------------
This switch tells the PowerQuest software
to use IDE instead of DMA transmission.
Try setting this switch to ON. (The default setting
for this switch is OFF (i.e., DMA transmission).)
Presumably they actually mean PIO, not IDE.
Paul Busby
>
> /IDE=ON
> --------------
> This switch tells the PowerQuest software
> to use IDE instead of DMA transmission.
>
> Try setting this switch to ON. (The default setting
> for this switch is OFF (i.e., DMA transmission).)
>
> Presumably they actually mean PIO, not IDE.
I'm a bit mystified with the naming as well. I would have thought DMA
mode would be faster than PIO & IDE. A minor point compared to the
doubling of throughput though.
Rosie
<rod_...@yahoo.com> writes
>
>George Pertoli <Georg...@excite.com> wrote in message
>news:rt28cv8e676m4ovse...@4ax.com...
>> Rod Speed <rod_...@yahoo.com> wrote
>>> George Pertoli <Georg...@excite.com> wrote
>
>>>> I have two computers running Drive Image 2002. The transfer
>>>> Speeds when making and image are dramatically different. My
>>>> older computer is actually faster than my newer one. How can this be?
>
>>> Its always been a real problem with DI, that big variation in the thruput.
>
>>> Try the /IDE=yes command line switch on the
>>> slow PC, that can make a hell of a difference.
>
>> Woooooooooooooooooooooohooooooooooooooooooooooooooooo
>
>> 1259mb per minute ......!!!! ;-)
>
>> Thanks for pushing me to try that Rod !!!
>
>> Now is there anyway to make that adjustment on the windows version ?
>> So when it reboots from windows to run, it does the same thing.
>
>Yeah, just edit the virtual floppy. The manual spells out how to
>do that pretty clearly. You're really just editing that command
>line in that virtual floppy in exactly the same way you did it with
>a real floppy. You just have to open the virtual floppy to do that.
>
where/how do I put this /IDE=yes switch? I have an XP1700+ (running at
1750) 512RAM and my throughput is about 195mb/m on 2 7200 drives UDMA4.
Does the switch go into the config.sys or what, and which floppy?
Thanks for your trouble.
--
rosie
Colin Sewell
[snip]
>Hi Rod. I'd like to try this on the real floppy to start with, but
>where/how do I put this /IDE=yes switch? I have an XP1700+ (running at
>1750) 512RAM and my throughput is about 195mb/m on 2 7200 drives UDMA4.
>Does the switch go into the config.sys or what, and which floppy?
>Thanks for your trouble.
Exit from Drive Image once it's runnning from the floppy, and then
type PQDI /IDE=ON. Or edit AUTOEXEC.BAT on the second floppy and add
/IDE=ON to the command line that starts PQDI.
Paul Busby
> Hi Rod. I'd like to try this on the real floppy to start with, but
> where/how do I put this /IDE=yes switch? I have an XP1700+ (running at
> 1750) 512RAM and my throughput is about 195mb/m on 2 7200 drives
> UDMA4.
> Does the switch go into the config.sys or what, and which floppy?
> Thanks for your trouble.
That's OK, though I'm not Rod ;)
You edit the autoexec.bat file on disc 2. Just add a space then /IDE=yes
to the PQDI line at the bottom. (or /ide=on):
PQDI /ide=yes.
Rod Speed
> Rod Speed wrote
>> And http://www.powerquest.com/support/primus/id1709.cfm says
Yeah, I had the same reaction. Maybe its more complicated than that
when its the only app running and you want max thruput or something.
I was gunna do a bit more research on that yesterday
but got sidetracked on something else instead. May
get around to that today. Currently just going thru
whats accumulated in usenet overnight.
Rosie
<cse...@telus.net> writes
completely forgotten that I now run my 2 drives off a Silicon Image SCSI
controller card in which case I suppose the above command will not make
any difference? Thanks for the prompt response.
My apologies!
--
rosie
Rosie
<m...@privacy.net> writes
--
rosie
Paul Busby
Adding the longer set of switches to the 2nd VFD file has speeded up
scheduled imaging as well, though interesting not by so much. Perhaps
this ain't the case 'cos running from QuickImage reboots before any
average thruput is displayed & always seems to be more than the
real-time counter would suggest.
I'm yet to try restore to see if that speeds up as well. My brother
commented that PQ maybe reluctant to mention this switch 'cos it might
be less reliable. My max figure of 699MB/min is with all options off &
high compression (no slower than med comp) with the image being stored
on the same disc. I'll check the QuickImage to my 2nd drive but I don't
expect anything startling 'cos the speed was the same before adding the
switches writing to either.
I hope the =yes works, I've used =on!
Rod Speed
Rosie <m...@purbeck.demon.co.uk> wrote in message
news:pgUh9JAb...@purbeck.demon.co.uk...
> >>Hi Rod. I'd like to try this on the real floppy to start with, but
> >>where/how do I put this /IDE=yes switch? I have an XP1700+ (running at
> >>1750) 512RAM and my throughput is about 195mb/m on 2 7200 drives UDMA4.
> >>Does the switch go into the config.sys or what, and which floppy?
> >>Thanks for your trouble.
>> Exit from Drive Image once it's runnning from the floppy, and then
>> type PQDI /IDE=ON. Or edit AUTOEXEC.BAT on the second
>> floppy and add /IDE=ON to the command line that starts PQDI.
> I think I may have been wasting your time here. When I posted
> I had completely forgotten that I now run my 2 drives off a Silicon
> Image SCSI controller card in which case I suppose the above
> command will not make any difference?
Yeah, the powerquest documentation is pretty poor
on that switch but it looks like its IDE specific, basically
controlling the mode used with an IDE interface.
Rod Speed
"Paul Busby" <m...@privacy.net> wrote in message news:ba639k$p5mbv$1...@ID-173588.news.dfncis.de...
> Rod Speed prematurely pulled the chain & typed:
> > Paul Busby <m...@privacy.net> wrote in message
> > news:ba5er7$pe75j$1...@ID-173588.news.dfncis.de...
> >> Rod Speed wrote
> >
> >>> And http://www.powerquest.com/support/primus/id1709.cfm says
> >
> >>> /IDE=ON
> >>> --------------
> >>> This switch tells the PowerQuest software
> >>> to use IDE instead of DMA transmission.
> >
> >>> Try setting this switch to ON. (The default setting
> >>> for this switch is OFF (i.e., DMA transmission).)
> >
> >>> Presumably they actually mean PIO, not IDE.
> >
> >> I'm a bit mystified with the naming as well. I would have
> >> thought DMA mode would be faster than PIO & IDE. A
> >> minor point compared to the doubling of throughput though.
> >
> > Yeah, I had the same reaction. Maybe its more complicated than that
> > when its the only app running and you want max thruput or something.
> >
> > I was gunna do a bit more research on that yesterday
> > but got sidetracked on something else instead. May
> > get around to that today. Currently just going thru
> > whats accumulated in usenet overnight.
> Adding the longer set of switches to the 2nd VFD file has speeded
> up scheduled imaging as well, though interesting not by so much.
You'll find some similar comments in groups.google seaching on
the /IDE=on string. That what I started to look at yestereday.
It also has different effects with image creation
and restoration which isnt very surprising.
> Perhaps this ain't the case 'cos running from QuickImage
> reboots before any average thruput is displayed & always
> seems to be more than the real-time counter would suggest.
Yeah, thats the other variable, whats displayed
and real thruput measured separately with a
stopwatch and the total data volume.
> I'm yet to try restore to see if that speeds up as well.
> My brother commented that PQ maybe reluctant to
> mention this switch 'cos it might be less reliable.
There are some comments on the cdrom
drive disappearing if that is used etc.
I guess it could be less reliable in a data corruption
sense because the UDMA modes do have CRCs and
PIO modes dont, on the IDE physical layer protocol.
> My max figure of 699MB/min is with all options off
> & high compression (no slower than med comp)
> with the image being stored on the same disc.
> I'll check the QuickImage to my 2nd drive but
> I don't expect anything startling 'cos the speed was
> the same before adding the switches writing to either.
Yeah, not surprising that it varys with the physical
drive when its basically specifying the IDE mode to use
at the physical layer protocol level and drives vary there.
> I hope the =yes works, I've used =on!
I've not seen any evidence that it matters except when
searching using google. I bet its just testing for both
when its parsing the command line switches at run time.
Markeau
> I'm yet to try restore to see if that speeds up as well. My brother
> commented that PQ maybe reluctant to mention this switch 'cos it
might
> be less reliable. My max figure of 699MB/min is with all options off
&
> high compression (no slower than med comp) with the image being
stored
> on the same disc. I'll check the QuickImage to my 2nd drive but I
> don't expect anything startling 'cos the speed was the same before
> adding the switches writing to either.
>
> I hope the =yes works, I've used =on!
No speed increase here with or without the switch and using either
=yes or =on ... but I'm doing high compression so maybe the cpu
crunching is the bottleneck ... getting around 700-750MB/min to a 2nd
drive ... 2.0GHz P4, 256MB RAM, 7200rpm drives
Paul Busby
> No speed increase here with or without the switch and using either
> =yes or =on ... but I'm doing high compression so maybe the cpu
> crunching is the bottleneck ... getting around 700-750MB/min to a 2nd
> drive ... 2.0GHz P4, 256MB RAM, 7200rpm drives
I don't use DI without compression so can't comment. ~700MB/min is what
mine has increased to! Someone I know was running with an Asus A7V333.
they changed some setting which is now forgotten & got a 3 fold increase
in performance. Some PCs seem to run DI at max speed anyway.