Running Access 97 Under XP
Gene Wirchenko
I have just picked up a bit of work on an Access 97 system. In
British Columbia, we have a change in the way that the taxes will be
computed coming up July 1.
Fortunately, I still have my Windows 98 box on my desk. I have
not used it in months, but I have to now as I can not get Access 97 to
install on my XP box. There is an installation error about not being
able to create system.mdw. (I am then told that the installation
completed successfully.) Access 97 will then not start because of the
missing file.
Does anyone know what I have to do to be able to run Access 97
under XP?
Sincerely,
Gene Wirchenko
Tom van Stiphout
wrote:
A97 can definitely be installed on XP.
I might rename all occurrences of system.mdw and try the install
again.
-Tom.
Microsoft Access MVP
Gene Wirchenko
<tom7744...@cox.net> wrote:
>On Thu, 24 Jun 2010 20:18:16 -0700, Gene Wirchenko <ge...@ocis.net>
>wrote:
>
>A97 can definitely be installed on XP.
Good.
>I might rename all occurrences of system.mdw and try the install
>again.
There were none. I did retry the installation (uninstalling
first) to the same effect.
I also tried copying the system.mdw from my 98 system, but when I
start Access 97 on my XP box, Access 97 blows up with an out-of-memory
error. Odd that: my 98 box has 192MB of RAM, and my XP box has 1.5GB
of RAM.
[snipped previous]
Sincerely,
Gene Wirchenko
Douglas J. Steele
news:dp8826da7sii6dl46...@4ax.com...
>
> I also tried copying the system.mdw from my 98 system, but when I
> start Access 97 on my XP box, Access 97 blows up with an out-of-memory
> error. Odd that: my 98 box has 192MB of RAM, and my XP box has 1.5GB
> of RAM.
The memory error is a common one. You need to ensure you've got the latest
upgrades to the Jet Database Engine. See
http://support.microsoft.com/kb/161255 for details.
Unfortunately, I'm not sure where you can get them anymore, as I don't
believe they're available through Windows Update.
--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
Co-author: Access 2010 Solutions, published by Wiley
(no e-mails, please!)
paii, Ron
I have run Access97 on everything from Windows98 though WindowsXP, It will
not run under Windows7 except in XP mode.
Two things to look for and change, before installing.
Search for the font file HATTEN.TTF, if found; rename it.
Search for other versions of Access, MSACCESS.exe, if found; rename it.
Install Access97, (I like to install it in a new Office97 folder instead of
the default, just to keep it separate for newer versions)
Run the check for service pack 2b, "SR2CHK.EXE"
If needed install Office97 service pack 1, "SR1OFF97.EXE"
If needed install Office97 service pack 2b, "SR2BOF97.EXE", (You will need
the Access97 disk to install the service pack)
If needed Install Jet service pack 3, "Jet35sp3.exe"
If new version of HATTEN.TTF existed, locate the newly installed HATTEN.TTF,
delete or rename it
Restore the original HATTEN.TTF
Optionally Restore the original MSACCESS.exe if you want to run both
versions of Access.
Access97 should now run.
"Gene Wirchenko" <ge...@ocis.net> wrote in message
news:ei7826p457os9uoe4...@4ax.com...
Tony Toews
>not used it in months, but I have to now as I can not get Access 97 to
>install on my XP box. There is an installation error about not being
>able to create system.mdw. (I am then told that the installation
>completed successfully.) Access 97 will then not start because of the
>missing file.
I'm running A97 fine on Win XP but then I'm running as administrator
which I should not be. And it sounds like you're running as a regular
user.
If I recall correctly in A97 the system.mdw file is placed in the
Windows System folder. However regular users can't update any files
in the Windows System folder. So you need to place that file
somewhere else. Toruble is I don't remember what the solution is.
And my memory may be faulty too.
You might night to see if the system.mdw file was created or create a
new system.mdw file and jonn to that file using the work group
admniistrator. But I may be missing some steps in here.
Tony
Douglas J. Steele
news:ion926p7tuvhm54ia...@4ax.com...
>
> I'm running A97 fine on Win XP but then I'm running as administrator
> which I should not be. And it sounds like you're running as a regular
> user.
I use Access 97 under WinXP, and I'm not Administrator on my machine.
> If I recall correctly in A97 the system.mdw file is placed in the
> Windows System folder.
Correct.
> 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.
Gene Wirchenko
>Checkout Tony's Access page at http://www.granite.ab.ca/accsmstr.htm
>
>I have run Access97 on everything from Windows98 though WindowsXP, It will
>not run under Windows7 except in XP mode.
>
>Two things to look for and change, before installing.
>Search for the font file HATTEN.TTF, if found; rename it.
>Search for other versions of Access, MSACCESS.exe, if found; rename it.
>
>Install Access97, (I like to install it in a new Office97 folder instead of
>the default, just to keep it separate for newer versions)
>Run the check for service pack 2b, "SR2CHK.EXE"
>If needed install Office97 service pack 1, "SR1OFF97.EXE"
>If needed install Office97 service pack 2b, "SR2BOF97.EXE", (You will need
>the Access97 disk to install the service pack)
>If needed Install Jet service pack 3, "Jet35sp3.exe"
>
>If new version of HATTEN.TTF existed, locate the newly installed HATTEN.TTF,
>delete or rename it
>Restore the original HATTEN.TTF
>Optionally Restore the original MSACCESS.exe if you want to run both
>versions of Access.
>
>Access97 should now run.
Thank you for the above. Access does now run, but SR2b was
rejected with
Microsoft Office 97 SR-2
The Microsoft Office 97 SR-2 patch cannot be applied to your computer.
Either Office 97 is not installed on this computer, or there are files
from multiple versions of Office 97 on this computer. Try installing
Office 97 or running the latest SR-1 patch to correct the problem. Or,
contact Microsoft Technical Support for further assistance.
OK
Office 97 is installed on my computer, and I have only one
version of it installed. I redownloaded the SR-1 patch to compare to
the one I installed, and it is the same one.
Any idea what is happening here?
[snip]
Sincerely,
Gene Wirchenko
paii, Ron
Did you run SR2CHK.EXE to check if your are ready for SR2b?
I have never had issues with SR2B after a clean install of Access97 if
SR2CHK passes.
You could try installing "SR2AOF97.EXE" before SR2B.
David W. Fenton
> Does anyone know what I have to do to be able to run Access 97
> under XP?
I'm running A97, A2000, A2003 and A2007 on this WinXP box.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
David W. Fenton
news:i02778$ohr$1...@news.eternal-september.org:
> If new version of HATTEN.TTF existed, locate the newly installed
> HATTEN.TTF, delete or rename it
> Restore the original HATTEN.TTF
> Optionally Restore the original MSACCESS.exe if you want to run
> both versions of Access.
The whole font renaming thing was really just a voodoo way of
forcing Access to fully re-register all its components.
David W. Fenton
news:i02ocj$hmg$1...@news.eternal-september.org:
> "Tony Toews" <tto...@telusplanet.net> wrote in message
> news:ion926p7tuvhm54ia...@4ax.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?
Salad
> Gene Wirchenko <ge...@ocis.net> wrote in
> news:ei7826p457os9uoe4...@4ax.com:
>
>
>>Does anyone know what I have to do to be able to run Access 97
>>under XP?
>
>
> I'm running A97, A2000, A2003 and A2007 on this WinXP box.
>
97->2000->2002->2003->2007... that was fine but installing an earlier
version after installing a later version posed problems.
Gene Wirchenko
>Did you run SR2CHK.EXE to check if your are ready for SR2b?
I had not, but I finally was able to find it and ran it. I got
the same error message I quoted above.
>I have never had issues with SR2B after a clean install of Access97 if
>SR2CHK passes.
>
>You could try installing "SR2AOF97.EXE" before SR2B.
That gave me the same error as well.
Sincerely,
Gene Wirchenko
Douglas J. Steele
news:Xns9DA2C1CA2AE96f9...@74.209.136.94...
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.
--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele/AccessIndex.html
Co-author: "Access 2010 Solutions", published by Wiley
(no private e-mails, please)
Tony Toews
wrote:
>> I'm running A97, A2000, A2003 and A2007 on this WinXP box.
>>
>I was under the impression if one installed
> 97->2000->2002->2003->2007... that was fine but installing an earlier
>version after installing a later version posed problems.
This is a myth that has been passed on by many folks including MVPs in
the past. MVPs have now stopped saying this due to my expereince and
my postings. <smile>
I have deliberately installed in random non chronological sequence 3,
4 or 5 versions of MS Access on my various systems over the past
decade. And other than the known A97 Hatten font problem I've
never had any problems.
Tony
David W. Fenton
news:K-CdnWpC-KEgpbjR...@earthlink.com:
This machine had A2003 (well, Office) installed first, and I added
the others later. I think the order was A2003, A97, A2000, A2007.
I've never had any issues except for the registration annoyance.
David W. Fenton
> 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
> "David W. Fenton" <XXXu...@dfenton.com.invalid> wrote in message
> news:Xns9DA2C1CA2AE96f9...@74.209.136.94...
>> "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_gmail.com> wrote in
>> news:i02ocj$hmg$1...@news.eternal-september.org:
>>
>>> "Tony Toews" <tto...@telusplanet.net> wrote in message
>>> news:ion926p7tuvhm54ia...@4ax.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.
Access Developer
> This machine had A2003 (well, Office) installed
> first, and I added the others later. I think the order
> was A2003, A97, A2000, A2007.
I, too, installed A97 on an XP machine that had Access 2003 installed first,
then Access 2002 so I could try out the latest Speed Ferret, and finally I
installed Office 97 so I could debug a problem for someone who was still
running A97. All are working just fine, though having done my Speed Ferret
tryout, I rarely open A2002 any more, and don't have much call for A97 these
days.
Larry Linson, Microsoft Office Access MVP
jwither
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" <XXXu...@dfenton.com.invalid> wrote in message
news:Xns9DA3B50045FBBf9...@74.209.136.94...
Douglas J. Steele
Okay, running Windows XP Professional, SP2 in a domain, I cannot create
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
Mark
> 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)
>
>
>
>
> > Tony Toews <tto...@telusplanet.net> wrote in
> >news:enrc269djn5246hki...@4ax.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/
>
> - Show quoted text -
For what it's worth ...
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
David W. Fenton
news:Q62dnY_Rd9NTHrXR...@westnet.com.au:
> From memory, the problem was that the installation script
> incorrectly validated the file size if a newer version of the
> font was already installed.
This contradicts what I recall Michael Kaplan having explained to us
about the situation.
David W. Fenton
> 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>"
All of the permissions in my non-domain C:/Users are not inherited,
but the modify permissions are not there. I wonder if that's a
customization on the part of your sysadmins.
> On the other hand, the Users group only has Read & Execute on
> "The Folder, subfolders and files" for the C: drive itself.
This is the same permission as I see on C:\Windows on a standalone
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.
gagea...@gmail.com
Patrick Finucane
There was a very small routine written by Michael (Michka) Kaplan that broke the...I don't know if this is correct...the admin password. He was upset people were charging for the crack as he felt it should be free. I was looking around for it but couldn't find it...I'm sure it's somewhere since it was on the internet.
Look at the code at this site from Jimmy Kerckhofs https://groups.google.com/forum/?hl=en#!topic/comp.databases.ms-access/ilYsCnJjnCg It has code from Michka but I don't think its the code I was thinking of...his may not have even been code...just some instructions.
Ulrich Möller
Am 09.12.2016 um 22:51 schrieb Patrick Finucane:
> On Friday, December 9, 2016 at 3:29:24 PM UTC-5, gagea...@gmail.com wrote:
>> On Thursday, June 24, 2010 at 11:18:16 PM UTC-4, Gene Wirchenko wrote:
>>> Hello:
>>>
>>> I have just picked up a bit of work on an Access 97 system. In
>>> British Columbia, we have a change in the way that the taxes will be
>>> computed coming up July 1.
>>>
>>> Fortunately, I still have my Windows 98 box on my desk. I have
>>> not used it in months, but I have to now as I can not get Access 97 to
>>> install on my XP box. There is an installation error about not being
>>> able to create system.mdw. (I am then told that the installation
>>> completed successfully.) Access 97 will then not start because of the
>>> missing file.
>>>
>>> Does anyone know what I have to do to be able to run Access 97
>>> under XP?
>>>
>>> Sincerely,
>>>
>>> Gene Wirchenko
>> Any chance I can revive this old thread with a new need? Access 97 is installed on an old Win XP box. I'm the registered owner of the single user copy. All security I set up then has come back to haunt me now. I cannot launch Access 97 w/o login credentials. Can I recover my ability to start A97 and open my old databases?
> I went to the Access Web and under the downloads section there was something from Terry Kreft called Secure. It might be able to help. http://access.mvps.org/access/resources/downloads.htm
>
> There was a very small routine written by Michael (Michka) Kaplan that broke the...I don't know if this is correct...the admin password. He was upset people were charging for the crack as he felt it should be free. I was looking around for it but couldn't find it...I'm sure it's somewhere since it was on the internet.
Look at: http://trigeminal.fmsinc.com/lang/1033/codes.asp?ItemID=5#5
Jürgen Meyer
>On Thursday, June 24, 2010 at 11:18:16 PM UTC-4, Gene Wirchenko wrote:
>> Hello:
>>
>> I have just picked up a bit of work on an Access 97 system. In
>> British Columbia, we have a change in the way that the taxes will be
>> computed coming up July 1.
>>
>> Fortunately, I still have my Windows 98 box on my desk. I have
>> not used it in months, but I have to now as I can not get Access 97 to
>> install on my XP box. There is an installation error about not being
>> able to create system.mdw. (I am then told that the installation
>> completed successfully.) Access 97 will then not start because of the
>> missing file.
>>
>> Does anyone know what I have to do to be able to run Access 97
>> under XP?
At first check, if the XP SP3 Service pack is already installed!
If not, then this will be the first step
Afterwards reinstall Access 97
This way it should work
When you try to install Access 97 from original CD on a PC with more than
1GB of ram (XP SP2), the install fails ("can't create system.mdb")
- If you try to manually copy the system.mdb file from another PC then the
launch of access fails, still when having more than 1GB of RAM ("out of
memory" error).
Without SP3 this might help:
- Starting with a PC under XP SP2
- REMORE RAM from the computer, to go under 1GB
- Install access 97 (no longer problem during the installation, but
execution still fails)
- REINSTALL RAM
- Download the MS Jet Database engine version 3.51 SP3 from microsoft.com
- Then Access is working again !
Juergen