We are running 4.0 also. We used to have the prowin32 errors something
fierce - 4-5 different workstations a day. Now I haven't heard a peep out
of prowin32. Hard to say specifically what helped, but I had to do a lot of
work to the network over the last 6 mo anyway, and sometime during that time
the prowin32 errors went away. I was too busy to give it a whole lot of
thought. But here's what was done.
Network
- New network cabling and 100mb/s switches
- Put a new server in charge, with Vantage on its own server
- Removed all protocols except TCP/IP to cut out extra net traffic
- Make NT4 service packs current thru 6a
Workstations
- Ditched anything under P166
- Upgraded memory - 64M min
- Bought GOOD network cards
- Reformatted and reinstalled Win98 on all workstations
got rid of win95 altogether
Vantage
- Upgraded to 4.00.904 and 9.0b
I seems that the prowin32 errors may have been produced by a bottleneck in
the system. I guess prowin32 doesn't like to wait. Now that I think of it,
all of these changes were probably mentioned at one time or another (one at
a time) by Vantage Tech Support in phone conversations as the probable cause
of prowin32 errors.
Of course, doing all that is out of the question in most cases, but
something in that list did the trick. Make it as stable as you can.
Gary Polvinale
Denton ATD
-----Original Message-----
From: Sandy Morse [mailto:smorse@...]
Sent: Thursday, April 19, 2001 12:04 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Prowin32 errors
Yes, we are at the most current version of software... also, thanks Wayne, I
am at service pack 6a so that should not be the problem.
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
fierce - 4-5 different workstations a day. Now I haven't heard a peep out
of prowin32. Hard to say specifically what helped, but I had to do a lot of
work to the network over the last 6 mo anyway, and sometime during that time
the prowin32 errors went away. I was too busy to give it a whole lot of
thought. But here's what was done.
Network
- New network cabling and 100mb/s switches
- Put a new server in charge, with Vantage on its own server
- Removed all protocols except TCP/IP to cut out extra net traffic
- Make NT4 service packs current thru 6a
Workstations
- Ditched anything under P166
- Upgraded memory - 64M min
- Bought GOOD network cards
- Reformatted and reinstalled Win98 on all workstations
got rid of win95 altogether
Vantage
- Upgraded to 4.00.904 and 9.0b
I seems that the prowin32 errors may have been produced by a bottleneck in
the system. I guess prowin32 doesn't like to wait. Now that I think of it,
all of these changes were probably mentioned at one time or another (one at
a time) by Vantage Tech Support in phone conversations as the probable cause
of prowin32 errors.
Of course, doing all that is out of the question in most cases, but
something in that list did the trick. Make it as stable as you can.
Gary Polvinale
Denton ATD
-----Original Message-----
From: Sandy Morse [mailto:smorse@...]
Sent: Thursday, April 19, 2001 12:04 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Prowin32 errors
Yes, we are at the most current version of software... also, thanks Wayne, I
am at service pack 6a so that should not be the problem.
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/