fnjlh1@acad3.alaska.edu (HARRIS JAY L) (01/28/91)
I've had bombs reading Pagestream 1.8 font data from disks run thru Neodesk 2.n, most of which showed bogus files. Reformatting and copying the font files from the OEM desktop seems to, so far, avert this problem. Anyone seen anything similar? Thanks fronm the Great White North.. j harris
weber_w@apollo.HP.COM (Walt Weber) (01/30/91)
In article <1991Jan28.073757.27686@ims.alaska.edu>, JAY HARRIS writes: |> |> I've had bombs reading Pagestream 1.8 font data from disks run thru |> Neodesk 2.n, most of which showed bogus files. Reformatting and copying the font |> files from the OEM desktop seems to, so far, avert this problem. Anyone |> seen anything similar? Thanks fronm the Great White North.. j harris There is a bug in the NEO 2.x version having to do with memory management and the way that NEO does a multi-file copy -- NEO uses all available memory to read as many files into memory that will fit, and then copies them all out to the destination, then refills the buffer. In some cases (I don't remember which) it does this wrong, which then results in corruption of either the data in some of the files, or of the file names and directories. I found this out by hitting the bug, then calling Gribnif. The solution I used was to do all copies through Universal Item Selector, called through the acc at the NEO desktop. NEO 3 appears to not have this bug. ...walt... Walt Weber Hewlett Packard Response Center 508-256-6600x6772 Chelmsford, MA, USA "The power of accurate observation is commonly called cynicism by those who have not got it" -George Bernard Shaw