2011-10-04 03:22:11 UTC
A very strange issue here, that I think I finally tracked down, but I just don't
I have a MCP2 FP6 system, SMP, using HPFS386. I've got 8 HPFS partitions on 2
separate disks, all either 60 or 64Gig in size, cache is set to 128Mbyte, only
enabled for the 4 'primary' partitions, since the remaining 4 (2nd physical
disk) are nightly hot-backups. Both disks are SATA drives.
The HPFS386 specific stuff is as follows:
3-23-04 10:17a 259689 0 hpfs386.ifs
9-30-03 6:11p 27237 405 CACHE386.EXE
9-30-03 6:11p 6845 404 HPFS386.DLL
9-30-03 6:11p 348965 403 NETAPI.DLL
9-30-03 6:11p 63766 417 NETAPI32.DLL
9-30-03 6:11p 6586 405 NETSPOOL.DLL
...so basically IP_8532 level for most of it with the exception of HPFS386.IFS
OK, so here is the problem, the last partition on each disk exhibits what I can
only call a 55 sec delay in saving a file.
So...as I open up one of my camera pics in PMView, re-size it, etc and attemp to
save to my last partition on a drive, the clock icon comes up...and sits there
for EXACTLY 55 secs...then if completes the save and PMView becomes responsive.
I tested this operation across all my partitions which is how I narrowed it down
to the problem being each last partition on the physical disk.
I had this same issue with Tame just last week...I moved the 'working directory'
to another spot, which of course worked out fine. But it didnt' dawn on me until
tonight when I was attempting to troubleshoot my PMView issue that it really was
one and the same thing. Tame would actually just HANG there while it attempted
to save the file once scanimage completed.
So...the question is: have any of you guys seen this? Is this related to a known
(maybe?) HPFS386 bug?
Thanks as always!