 | |
Running Access 97 Under XP
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: Running Access 97 Under XP -
06-28-2010
, 06:13 AM
|
Tony Toews <ttoews (AT) telusplanet (DOT) net> wrote in news:enrc269djn5246hki3qbr7ctqphpha229v (AT) 4ax (DOT) com: And other than the known A97 Hatten font problem I've never had any problems. Aiee! There is no such thing as a Hatten font problem. There was nothing wrong with that font, and the font didn't cause the issue. But if the install process found the Hatten font missing, it would trigger a reinstall that would properly register everything. In other words, renaming the font was just a simple way to trigger the fix. It wasn't the fix itself, because there was nothing wrong with the font in the first place. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#22
| |||
| |||
|
|
"Douglas J. Steele" <NOSPAM_djsteele (AT) NOSPAM_gmail (DOT) com> wrote in news:i05222$9e4$1 (AT) news (DOT) eternal-september.org: "David W. Fenton" <XXXusenet (AT) dfenton (DOT) com.invalid> wrote in message news:Xns9DA2C1CA2AE96f99a49ed1d0c49c5bbb2 (AT) 74 (DOT) 209.136.94... "Douglas J. Steele" <NOSPAM_djsteele (AT) NOSPAM_gmail (DOT) com> wrote in news:i02ocj$hmg$1 (AT) news (DOT) eternal-september.org: "Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote in message news:ion926p7tuvhm54ia4nf2t3lm5f915ajls (AT) 4ax (DOT) com... However regular users can't update any files in the Windows System folder. Don't believe that's generally the case. Definitely I can write to that folder (and given how locked down our machines are, I can't imagine that we would have relaxed built-in security rules anywhere! And given that a System.ldb file is opened whenever you're using the System.mdw file, it really wouldn't make sense that the file would be written to a write-protected folder. That's odd, as the default permissions on the Windows folder have been read-only for users starting with Win2000. Power Users have modify permission. Are you sure you're not running as a member of the Power Users group? Positive. It's possible that they perverted the default permissions, but I'd be extremely surprised, since generally we tighten up security, not loosen it, in our environment. When I get back to the office on Monday, I'll try and remember to check the permissions on the folder. I'm pretty sure that running in a domain environment you're running as a user and just because you're in a domain you don't get more permissions than you'd get running as an individual. The same read-only limitations apply to the root of C: and to the programs folder, BTW, and this has been so since the introduction of Windows 2000, which was the first version of Windows to move the user profiles out of the Windows folder in order that the Windows folder could be properly locked down without having special permissions on the profiles folder. |
folders on the C: drive, but I can create folders in the C:\Windows folder
and the C:\Windows\System32 folder.
Looking at the Advanced Security Settings for both C:\Windows and
C:\Windows\System32, the Users group has Read & Execute on "This folder,
subfolders and files", and has Modify on "This folder only" and "Files
only", all of them "<not inherited>"
On the other hand, the Users group only has Read & Execute on "The Folder,
subfolders and files" for the C: drive itself.
--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
Co-author: Access 2010 Solutions, published by Wiley
(no e-mails, please!)
#23
| |||
| |||
|
|
On my computer, the installer crashed on the Hatten font installation, as recorded by the error in the installation log, causing the installation to not be completed. Non-completion of the installation meant that the registration was not attempted. Removing or correcting the Hatten font line in the installation script allowed the script to proceed to registration. From memory, the problem was that the installation script incorrectly validated the file size if a newer version of the font was already installed. (david) "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid> wrote in messagenews:Xns9DA3B50045FBBf99a49ed1d0c49c5bbb2 (AT) 74 (DOT) 209.136.94... Tony Toews <tto... (AT) telusplanet (DOT) net> wrote in news:enrc269djn5246hki3qbr7ctqphpha229v (AT) 4ax (DOT) com: And other than the known A97 Hatten font problem I've never had any problems. Aiee! There is no such thing as a Hatten font problem. There was nothing wrong with that font, and the font didn't cause the issue. But if the install process found the Hatten font missing, it would trigger a reinstall that would properly register everything. In other words, renaming the font was just a simple way to trigger the fix. It wasn't the fix itself, because there was nothing wrong with the font in the first place. -- David W. Fenton * * * * * * * * *http://www.dfenton.com/ usenet at dfenton dot com * *http://www.dfenton.com/DFA/- Hide quoted text - - Show quoted text - |
I use two CDs:
1. Office 97 Professional
2. and a second CD which contains the following:
A. a folder with the following Office97 fonts:
comic.ttf
comicbd.ttf
tahoma.ttf
tahomabd.ttf
B. a second folder with those same fonts, but Office 2007 versions.
C. a copy of SR2AOF97.EXE (SR-2)
-- I also have a copy of SR1OFF97.EXE to install SR-1 first if needed,
but my Office 97 installation disk installs SR-1 by default.
D. a copy of Jet35sp3.exe
To install Access 97 alongside Office 2007, I insert the second CD
first. I select the four Office 97 fonts on the CD, right-click and
choose "install".
If Access 2007 exists, I locate the msacess.exe file on the hard
drive ... usually under Program Files\Microsoft Office\Office12 ...
and temporarily rename it (e.g., msaccess.xxx)
I create a new folder to which I will install Access 97 , e.g.:
Program Files\Microsoft Office\Office97
I insert the Office 97 installation CD, choose Custom, unselect all,
then re-select all components for Access 97 and install it to Program
Files\Microsoft Office\Office97.
Note: If installing on a Vista or Windows 7 computer, I'll look for
the installation (setup) file on the CD, right-click and choose "run
as administrator".
During the installation process, I'll be given a registration number.
I copy this down because it will be asked for during the installation
of SR-2.
After Access 97 has installed, I'll re-insert the second CD and
install SR2AOF97.EXE and then Jet35sp3.exe (right-click and choose
"run as administrator" on Vista or Win 7).
Lastly, I'll select the four Office 2007 fonts on the CD, right-click
and choose "install". If Access 2007 exists, I'll rename msaccess
(under Office12) back to msaccess.exe.
Mark
#24
| |||
| |||
|
|
From memory, the problem was that the installation script incorrectly validated the file size if a newer version of the font was already installed. |
about the situation.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
#25
| |||
| |||
|
|
Looking at the Advanced Security Settings for both C:\Windows and C:\Windows\System32, the Users group has Read & Execute on "This folder, subfolders and files", and has Modify on "This folder only" and "Files only", all of them "<not inherited>" |
but the modify permissions are not there. I wonder if that's a
customization on the part of your sysadmins.
Quote:
|
On the other hand, the Users group only has Read & Execute on "The Folder, subfolders and files" for the C: drive itself. |
PC, and it's what I'm accustomed to seeing since Win2000. It's also
the permissions I assume for anything I do with Access.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.