By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,501 Members | 1,678 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,501 IT Pros & Developers. It's quick & easy.

wininet and urlmon in use during A97 runtime rollout

P: n/a
MLH
My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.
Nov 30 '05 #1
Share this Question
Share on Google+
10 Replies


P: n/a
MLH <CR**@NorthState.net> wrote in
news:0r********************************@4ax.com:
My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.


This is the type of thing that caused me long ago to vow never to
use any of the IE and Internet related components of Windows in an
Access application. There was also the terribly problem of
cross-version incompatibilities.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 30 '05 #2

P: n/a
MLH
I see your point.
Nov 30 '05 #3

P: n/a
The nice thing about the old install system is that
you can actually go into the files and change them.

In fact, there is nothing magic about the wizard: it
just writes out a couple of text files and them compresses
everything.

You can use "Expand" to uncompress the files, but with
modern storage, I never compressed the build anyway.

I just deleted urlmon and wininet from the build. Those
files aren't required for most applications. Those files
aren't required at all unless you are installing to an
unpatched copy of win 95.

You can modify the wizard to do the kind of build you
want, but I never bothered: I just modified the file
list to change the file sizes every time I did a new
release.

(david)

"MLH" <CR**@NorthState.net> wrote in message
news:0r********************************@4ax.com...
My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.

Nov 30 '05 #4

P: n/a

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
MLH <CR**@NorthState.net> wrote in
news:0r********************************@4ax.com:
My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.


This is the type of thing that caused me long ago to vow never to
use any of the IE and Internet related components of Windows in an
Access application. There was also the terribly problem of
cross-version incompatibilities.


Those files are always in the 97 runtime distribution. It would not matter what
was being used in the Access app.

Getting that message is just an indication that the files on the target PC are
older versions than what is in the distribution. I have never seen a problem
with just hitting [Ignore]. The only way to avoid it is to keep all of the
files in the runtime distribution in as old a version as you can.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Dec 1 '05 #5

P: n/a
"Rick Brandt" <ri*********@hotmail.com> wrote in
news:Fq*******************@newssvr14.news.prodigy. com:

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
MLH <CR**@NorthState.net> wrote in
news:0r********************************@4ax.com:
My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.
This is the type of thing that caused me long ago to vow never to use any of the IE and Internet related components of Windows in
an Access application. There was also the terribly problem of
cross-version incompatibilities.


Those files are always in the 97 runtime distribution. It would
not matter what was being used in the Access app.


Er, what does the runtime have to do with the larger question?

Secondly, some of the components might be replaced by some other
installer after the runtime was installed. Note that I mentioned
IE,
which was notorious for its later versions not working with A97.
Getting that message is just an indication that the files on the
target PC are older versions than what is in the distribution. I
have never seen a problem with just hitting [Ignore]. The only
way to avoid it is to keep all of the files in the runtime
distribution in as old a version as you can.


I avoid outside dependencies in my Access apps whenever possible,
except for API calls, which are always guaranteed to work.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Dec 1 '05 #6

P: n/a
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
"Rick Brandt" <ri*********@hotmail.com> wrote in
news:Fq*******************@newssvr14.news.prodigy. com:

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
MLH <CR**@NorthState.net> wrote in
news:0r********************************@4ax.com:

My A97 runtime installations are sometimes paused
during the install process prompting user with messages
saying the files are in use. Generally, I tell them to click
IGNORE. Although I haven't had any noticeable related
impact in past installations, I cannot help but wonder
what is going on and if my installations are jeopardized
because of something important I'm overlooking.

This is the type of thing that caused me long ago to vow never to use any of the IE and Internet related components of Windows in
an Access application. There was also the terribly problem of
cross-version incompatibilities.
Those files are always in the 97 runtime distribution. It would
not matter what was being used in the Access app.


Er, what does the runtime have to do with the larger question?


The "original" question was why is MLH seeing these warnings when installing his
97 runtime app. My point was that getting those warnings has nothing to do with
"outside dependencies". If he was packaging and installing a data only mdb with
zero references he would still have gotten those messages.
Secondly, some of the components might be replaced by some other
installer after the runtime was installed. Note that I mentioned
IE,
which was notorious for its later versions not working with A97.
This is true.
I avoid outside dependencies in my Access apps whenever possible,
except for API calls, which are always guaranteed to work.


As do I, but that would not prevent these messages during install of the
runtime.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Dec 1 '05 #7

P: n/a

"Rick Brandt" <ri*********@hotmail.com> schreef in bericht news:bS*******************@newssvr11.news.prodigy. com...

The "original" question was why is MLH seeing these warnings when installing his
97 runtime app. My point was that getting those warnings has nothing to do with
"outside dependencies". If he was packaging and installing a data only mdb with
zero references he would still have gotten those messages.


Yep, that's also my experience.
In almost all my A97-runtime-distributions (zero dependencies) I got these two warnings.
I *always* ignored them without any other problems, but I was a bit pissed, because I did *not* want to deliver apps that way.
I like 'proper' install sets ... without any warnings. I like my users to think. "hey, that is working great."

In 'my days of Access 2.0' I also used a runtime install set.
When using User Level Security I *had* to 'manually' set certain things 'right'.
The runtime-install was always messing-up the mda (and I believe the ini-file) that was to be used ...
Aaarrrrrgggghhhhhhhhhhhh !!!!!!
Eventually I 'got this right' by means of a batch-file that I started automatically after the improper-install.

I *never* managed to 'get right' the Access 97-runtime-install (without warnings that is ...)
For a co-project I was involved with, we once made a A97-Wise-install with the SageKey script. It worked !!

I hate to have to buy third-party software (Wise + Sagekey) only to get software that I payed for to work properly ...
I still think it is a real shame that MS did such a terrible job at this.
Later developer-editions are the same misery I believe from postings here ??

For me: I will *never* buy a developers-kit again until it is a proper one.
A year ago or so I decided (as others here) to deliver only to clients that have (or will buy) Access installed on their system.
I also was thinking of eventually delivering A97 installs on 'clean' systems. (see further on)
(I don't want the install to mess up a system where Office is installed...)

Two weeks ago I had to re-install a A97-program for a client on two brand new PC's.
Guess what??
The A97-runtime-install that I have used *for years* for this client (with the 2 warnings MLH asked about) failed !!
It just did not work. I kept recieving GPF's ...
Client had Win '98 SE before, but on these new PC's we had Windows XP-home sp2 installed. *Nothing* else!
So I decided to convert the app to A2k and tried to install Office 2000 instead of the runtime.
==>> I did 'uninstal' the runtime of course!!
Guess what??
The Office2000 install failed !! This was ONLY because I *did have tried* to install the A97-runtime.
I even tried to get back to the original registry and all. (used the WinXP /restore or whatever switch.)
Even that did not work !!

I had to *completely rebuild!!* that system... Aaarrrrrgggghhhhhhhhhhhh !!!!!!
After I did that I installed Office 2k and the app worked...

So now I am stuck with two versions (A97 AND A2k) of the *same* app running in several shops.
I am still happy to be able to use the same A97 backend for both versions.
But I really thank God (almost daily) that the A2k mde runs with A2k2 and A2k3 ...

Sorry: had to get this off my chest ... ;-)

Arno R
Dec 1 '05 #8

P: n/a

"david epsom dot com dot au" <david@epsomdotcomdotau> schreef in bericht news:43*********************@lon-reader.news.telstra.net...
The nice thing about the old install system is that
you can actually go into the files and change them.

In fact, there is nothing magic about the wizard: it
just writes out a couple of text files and them compresses
everything.

You can use "Expand" to uncompress the files, but with
modern storage, I never compressed the build anyway.

I just deleted urlmon and wininet from the build. Those
files aren't required for most applications. Those files
aren't required at all unless you are installing to an
unpatched copy of win 95.

You can modify the wizard to do the kind of build you
want, but I never bothered: I just modified the file
list to change the file sizes every time I did a new
release.

(david)


Hi david,

I remember that I have been looking at the wizard settingssome years ago to delete these files from the install.
No luck. Maybe I have been overlooking things??
I thought these filess were part of standard-Access-files or so?

Never mind though, but I am still interested to know how *exactly* you delete the two files from the build.
Can you just open the setup.stf file in Notepad and delete the lines?

I am using A2k nowadays but one never knows.
Thanks

Arno R
Dec 1 '05 #9

P: n/a
I don't have the files in front of mean, and it has
been a long time since I looked.

You can't just delete the files from setup.lst,
but you can change the command there from something
like "older" to something like "never"

To delete the files entirely, you have to remove
them from the script file, which is ???? setup.???
And you have to follow through the script file, to
remove any references to any lines you delete. (Or
you can replace the urlmon and wininet lines with
something harmless)

When working with these files, you have to be a bit careful
about tabs and white space.

Yes, urlmon and wininet are a standard part of the
Access 97 installation. A useless error prone part,
not required by most applications, and even then only
required on an unpatched version of Win 95.

(david)

"Arno R" <ar***********@tiscali.nl> wrote in message
news:43**********************@text.nova.planet.nl. ..

"david epsom dot com dot au" <david@epsomdotcomdotau> schreef in bericht
news:43*********************@lon-reader.news.telstra.net...
The nice thing about the old install system is that
you can actually go into the files and change them.

In fact, there is nothing magic about the wizard: it
just writes out a couple of text files and them compresses
everything.

You can use "Expand" to uncompress the files, but with
modern storage, I never compressed the build anyway.

I just deleted urlmon and wininet from the build. Those
files aren't required for most applications. Those files
aren't required at all unless you are installing to an
unpatched copy of win 95.

You can modify the wizard to do the kind of build you
want, but I never bothered: I just modified the file
list to change the file sizes every time I did a new
release.

(david)


Hi david,

I remember that I have been looking at the wizard settingssome years ago to
delete these files from the install.
No luck. Maybe I have been overlooking things??
I thought these filess were part of standard-Access-files or so?

Never mind though, but I am still interested to know how *exactly* you
delete the two files from the build.
Can you just open the setup.stf file in Notepad and delete the lines?

I am using A2k nowadays but one never knows.
Thanks

Arno R
Dec 2 '05 #10

P: n/a

"david epsom dot com dot au" <david@epsomdotcomdotau> schreef in bericht news:43*********************@lon-reader.news.telstra.net...
I don't have the files in front of mean, and it has
been a long time since I looked.

You can't just delete the files from setup.lst,
but you can change the command there from something
like "older" to something like "never"

To delete the files entirely, you have to remove
them from the script file, which is ???? setup.???
And you have to follow through the script file, to
remove any references to any lines you delete. (Or
you can replace the urlmon and wininet lines with
something harmless)

When working with these files, you have to be a bit careful
about tabs and white space.


Thanks david,

I remember this yes. That's exactly why I was asking *exactly* how to do this ...
Maybe I will try to tweak the setup files again one of these days.
But as I wrote in another post in this thread: Nowadays I am having other problems with this setup also.

Arno R
Dec 2 '05 #11

This discussion thread is closed

Replies have been disabled for this discussion.