File named c:\Program created!!! EEEK!
Sue Sloan
The problem arises from older software that looks for files using the DOS path instead of the full path name. Compuserve version 4 is one such program, FYI. It looks for critical files in c:\PROGRA~1\FCABINET for example, and your file throws things off because your file becomes c:\PROGRA~1 and the Program Files becomes c:\PROGRA~2\FCABINET.
I only know this because this totally trashed my "cabinet" full of folders and email messages that goes back to 1999!!! It is NOT repairable!
Please provide a patch for this problem or at least add it to your FAQs as it will trash many programs that depend on the old DOS path naming conventions.
Sue Sloan
The Liquidator
I found that with SO5, the SO6 beta and Openoffice1 is that the best
directory to install to is c:\ and forget about the program files bit. I
found that the SO6 beta had problems with long file names. I suggest you
uninstall SO6, delete any files left and reinstall as above.
I have to say that I am surprised that Windows can search for critical
files in a folder that did not exist until you installed SO6! Whatever
the cause, I would suggest the above would solve the problem for future
users.
Hopefully you have done regular backups and are able to minimise the
impact of this.
Ian
Sun Microsystems - Marcus Lange
Thema File named c:\Program created!!! EEEK!:
Hi Sue,
I don't know how you did the installation that this behaviour can occur.
But I don't thing that this is bug.
Please try to uninstall StarOffice and delete the any entry for
StarOffice 6.0 in the file "sversion.ini" (can be found somewhere in the
Windows subdirs), if an entry in the file is pointing to a StarOffice 6.0
path.
Then re-install StarOffice. When the default directory is shown (e.g.,
"C:\Program Files\StarOffice6.0") you can change it into "C:\Office60".
Then you will not have these problems.
HTH
Best regards
Marcus Lange
StarOffice Product Support
Sue Sloan
2) It is the presence of a c:\Program file that evidently was created by SO6 that I am complaining about. Your program should NOT install anything in the root directory of a Windows system, and this entry in particular has caused one of my other programs to misbehave and damage a file of emails going back over 4 years.
If you must put a file in c: then please do not name it "Program"!
Sue Sloan
Sun Microsystems - Marcus Lange
Thema Re: File named c:\Program created!!! EEEK!:
Hi Sue,
> 1) I am happy with StarOffice installed in c:\Program Files\StarOffice6.0
-- that is not a problem.
fine :-)
> 2) It is the presence of a c:\Program file that evidently was created by
SO6 that I am complaining about. Your program should NOT install anything
in the root directory of a Windows system, and this entry in particular has
caused one of my other programs to misbehave and damage a file of emails
going back over 4 years.
Like I wrote in my previous mail, I don't think that this was done by
StarOffice automatically.
But I also don't know how it occured. ;-)
> If you must put a file in c: then please do not name it "Program"!
Please believe me, StarOffice is not creating a file indepentently in the
root directory of a drive. Also not with a name which could be mixed up
very easy. ;-)
If the dir "C:\Program Files" is still existing and the programs are
still installed in the subdirs, then you should be able to delete the
file without problems.
Sue Sloan
====================================================
usage: xcons [<serverdb>] <Command> [<Interval> [<Repeat>]]
database :: <serverdb>
Commands:
cancel the command of task :: CANCEL <taskindex>
kill the session of task :: KILL <taskindex>
show statistics/states :: SHOW IO
SHOW STORAGE
SHOW TASKS
SHOW VERSIONS
SHOW REGIONS
SHOW STATE
SHOW RTE
SHOW ALL
====================================================
Sue Sloan