Server: Client: AlphaServer 2100 4/275 Windows 95 VMS 6.0 PW for Win 95 v. 1.0 PW Server V5.0C Office installed to run from the Server I have searched the archives on Dejanews, but I did not see anything regarding this problem. Computer Systems Technician - NH Community Technical College System">
 
 
 
 
Categories
Home
Career For College
Tech Schools
Trade Schools
Education Articles
Vocational Centers
Site Map

Articles
Technical Schools
Trade Schools
Career Schools
Education
Online High School Courses
Online High School
Request an Article
   
Nh Community Technical College

Get the Ultimate Resume Guide for Computer Jobs and get the job of your dreams!

Question:
I tried posting this once before, but I think my news server hiccuped and I didn't see any responses on the article. Sorry if it's a repeat. I am currently running into some problems with Office 95. The admin install itself runs fine with the updated OFF95_BB.DLL file. After I run the workstation setup my problems begin. The setup appears to complete without error, but closer inspection reveals that the Icons for office application files do not take on the originating application icon. Instead they take on the form of an unknown file. However, if I double click the file in explorer, the correct app starts and the file is called into it. The same holds true for the "New Office Document" folder, the icons are incorrect and the long filenames do not appear, instead I only get the actual dos version of the filename (8 char.). While this is not a major problem for myself, my users will scream. My environment is:

Server: Client: AlphaServer 2100 4/275 Windows 95 VMS 6.0 PW for Win 95 v. 1.0 PW Server V5.0C Office installed to run from the Server I have searched the archives on Dejanews, but I did not see anything regarding this problem. Computer Systems Technician - NH Community Technical College System




Answer:
I think there were a few responses to this post, or one like it, a couple of weeks ago.

Windows 95 has a 'feature' where it only connects to network drives when the user reads or writes that drive - it makes the startup much quicker. Unfortunately 95 also wants to verify the program icons on every startup. Result is that icons for executables residing on network shares are replaced by 'generic' ones. I believe there is a registry setting which forces a connect to each network drive at logon; that should fix the icons at the cost of a longer login process.

I'm not sure what is happening with the filenames. Are the files on a FAT share?



Submit your comment or answer



 
| Home | Career For College | Tech Schools | Trade Schools | Vocational Centers | Site Map | Privacy Policy |