On 5 Apr 2004 at 10:46, Eric Dannewitz wrote: > David W. Fenton wrote: > > >I think you're completely full of beans. > > Wow, we are getting kind of nasty here.
??? Nasty? "Full of beans" is nasty? > Have you tried running Disk Check on your filesystem? . . . Well, yes. No errors. > . . . Windows Xp and > 2000 are not the safest filesystems in the world, and I just had an XP > computer totally mess up it's filesystem after I ran XP's disk > defragmenter. I can't speak about XP, but NTFS 5 (the file system in Win2K and WinXP) is the safest and most reliable file system Microsoft has ever provided. I have had no problems with corrupted file systems on any NT-based system I've ever administered or owned, which would be dozens of such systems since 1998 (when I first started working with NT). > Anyhow, I'd try running XP's disk check. Easiest way is to open a > Command Line and type CHKDSK C:/ F and YES when it asks you if you > want to do it on reboot. Then after it runs, do a defrag. > > Also turning on SMART for your HD is a good idea. That is done in > BIOS. > > Good luck The symptoms of the problem don't point to hard drive problems at all. The fact that another individual running a different OS and a different PC (in a completely different country, I might add) kind of shows that the file system on my PC has nothing to do with it. The ETF import shows the file system has nothing to do with it. The shorter version of the file shows the file system has nothing to do with it. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
