OOo 2.04GA hammering disk if "Open Document..."
ICON accessed

Hi all,

Although I subscribed to the original OO 1.14[?] version, I never did get 
around to installing it -- I have been still using Star Office 5.1A until 
now, but after receiving an e-mail from info@mensys.nl advising me that I 
had a download of OOo 2.04 awaiting me, albeit without support, I just 
installed it,and I'm quite impressed with it.

However if I access the WPS icon for "Open Document...", it really
hammers 
the disk with about 25 mixed [eCS-OS/2-W2K-Linux-DOS] partitions 
[FAT16-FAT32-HPFS-JFS-Reiser-EXT2], sounding like a machine-gun rat-a-tat.

I could partially understand this on the initial access - but why does it 
do this on every single occasion. SO 5.1A didn't exhibit this behaviour at 
all when  creating its own drive-tree [Workplace?]

Any suggestions to eliminate these destructive-sounding actions?

Regards,
Mike

Mike O'Connor wrote:

> Hi all,

> Although I subscribed to the original OO 1.14[?] version, I never did get 
> around to installing it -- I have been still using Star Office 5.1A until 
> now, but after receiving an e-mail from info@mensys.nl advising me that I 
> had a download of OOo 2.04 awaiting me, albeit without support, I just 
> installed it,and I'm quite impressed with it.

> However if I access the WPS icon for "Open Document...", it
really hammers 
> the disk with about 25 mixed [eCS-OS/2-W2K-Linux-DOS] partitions 
> [FAT16-FAT32-HPFS-JFS-Reiser-EXT2], sounding like a machine-gun rat-a-tat.

> I could partially understand this on the initial access - but why does it 
> do this on every single occasion. SO 5.1A didn't exhibit this behaviour at

> all when  creating its own drive-tree [Workplace?]

> Any suggestions to eliminate these destructive-sounding actions?

> Regards,
> Mike

forgot to say this running on eCSV2.0Beta4

Mike

In <be833a316f16f3fb499516520c126639$1@news.ecomstation.com>, on 06/07/07

     at 10:35 AM, mikeoc@internode.on.net (Mike O\'Connor) said: >Any
suggestions to eliminate these destructive-sounding actions?

No.  It's using LVM to discover the structure of the drives.  I complained
about this during the beta, and Paul Ratcliffe said that he'd filed a bug
report and complained to the authors several times without their changing
it.  That will happen every time you access the file menu if you want it
to change to a different drive.  I find it very annoying.

Mike Snyder

On 06/07/07 11:03 am msnyder1 at cfl dot rr dot com wrote:

> suggestions to eliminate these destructive-sounding actions?
> 
> No.  It's using LVM to discover the structure of the drives.  I complained
> about this during the beta, and Paul Ratcliffe said that he'd filed a bug
> report and complained to the authors several times without their changing
> it.  That will happen every time you access the file menu if you want it
> to change to a different drive.  I find it very annoying.


I agree that it's very annoying. At first I thought that it was trying 
to access Drives C: and D: (FAT, not necessarily "clean") before
trying 
other drives, but that's obviously not the case.

Hope they get it fixed soon.

-=-

On Thu, 07 Jun 2007 11:38:31 -0400, Alan Beagley <cyberpastor@att.net>
wrote:

>> No.  It's using LVM to discover the structure of the drives.  I
complained
>> about this during the beta, and Paul Ratcliffe said that he'd filed a
bug
>> report and complained to the authors several times without their
changing
>> it.  That will happen every time you access the file menu if you want
it
>> to change to a different drive.  I find it very annoying.

A slight exaggeration. I only complained about it once.

> I agree that it's very annoying. At first I thought that it was trying 
> to access Drives C: and D: (FAT, not necessarily "clean") before
trying 
> other drives, but that's obviously not the case.
> 
> Hope they get it fixed soon.

That depends on whether they think it is broken or not. I got the impression