We have been trying to use MAX 7 on a Peer to Peer network with three users for months but the computers seem to all have different problems with crashes and powerdown problems.
Has anyone else having problems?
Original Post
Replies sorted oldest to newest
You say you are having powerdown and crashing problems, is this when running Maximizer or just general usage of the machines.
By powerdown, what exactly do you mean?
Maximizer closing or the machine itself not turning off properly?
What operating system are you using? if it is not powering down properly, is it Win98?
I need a bit more detail, a machine crash is usually a faulty driver somewhere, and powerdown problems (if you are refering to the computer) may be a machine problem or Windows problem (98 especially)
CABC Support
support@cabc.co.uk
By powerdown, what exactly do you mean?
Maximizer closing or the machine itself not turning off properly?
What operating system are you using? if it is not powering down properly, is it Win98?
I need a bit more detail, a machine crash is usually a faulty driver somewhere, and powerdown problems (if you are refering to the computer) may be a machine problem or Windows problem (98 especially)
CABC Support
support@cabc.co.uk
We are using 98SE and the crash is while powering down normally with this error W3dbsmgr in w3comsrv.dll. Two of the three computers get this error. The computer that has the database doesn't but it just stops running every few minutes with the hour glass on the screen.
Hope this helps as tech support at Max has not be any help.
Hope this helps as tech support at Max has not be any help.
W3DBSMGR might Freeze Windows 95/98 on Exit
When running Pervasive.SQL 2000 applications on Windows 95 or Windows 98, the Task list could show one or more instances of W3DBSMGR in memory, even after all applications are closed and the engine is shut down.
NETBIOS keeps an open thread to the W3DBSMGR, causing it to remain in memory, even though the taskbar icon has gone.
If NETBIOS is not necessary to your application, disable it as a supported protocol on the machine where the engine resides.
How To Disable NETBIOS as a Supported Protocol
1. Load Pervasive Control Center (Start>Programs>Pervasive) and open the Configuration Utility by clicking on the crosses next to Pervasive.SQL 2000i Engines>Machine name>Configuration>Server>Communication protocols.
2. Double-click on "Supported protocols" in the right pane.
3. "Microsoft NETBIOS" is listed as a supported protocol by default.
4. Highlight it in the "Selected" listbox, then click on the "<" button to
remove it from the list.
5. Click the "OK" button,
6. Now go to the Client key in the Configuration string and repeat steps 2>5
then apply your changes by clicking on the Apply button
(button with a red "!" on it")
or
by clicking "Settings", "Apply All" in the menu.
7. Close the Control Centre, stop the engine, and kill all open W3DBSMGR processes in the task manager (Ctrl-Alt-Del once!).
8. Then re-start it (it needs to be running on the machine with the data, the Gateway machine)
Do you have a Startup shortcut to start the pervasive engine?
Try going to Windows Explorer, Drag and Drop or Copy and Paste the file C:\Pvsw\Bin\W3DBSMGR.EXE into your Windows start up folder as a ShortCut, via either your Start Menu at the bottom left of your machine or if you know its exact location in Windows Explorer, do it that way.
Typically C:\WINDOWS\Start Menu\Programs\Startup for Windows 9X or ME.
When it is in your start up folder, Right click on it then select properties>Shortcut and where it says Target it should say;
C:\Pvsw\Bin\W3DBSMGR.EXE -BTRV
(You add the -BTRV) click apply then OK
Reboot Windows
Regards
CABC Support
support@cabc.co.uk
[This message has been edited by CABC Support (edited 25 April 2002).]
[This message has been edited by CABC Support (edited 25 April 2002).]
When running Pervasive.SQL 2000 applications on Windows 95 or Windows 98, the Task list could show one or more instances of W3DBSMGR in memory, even after all applications are closed and the engine is shut down.
NETBIOS keeps an open thread to the W3DBSMGR, causing it to remain in memory, even though the taskbar icon has gone.
If NETBIOS is not necessary to your application, disable it as a supported protocol on the machine where the engine resides.
How To Disable NETBIOS as a Supported Protocol
1. Load Pervasive Control Center (Start>Programs>Pervasive) and open the Configuration Utility by clicking on the crosses next to Pervasive.SQL 2000i Engines>Machine name>Configuration>Server>Communication protocols.
2. Double-click on "Supported protocols" in the right pane.
3. "Microsoft NETBIOS" is listed as a supported protocol by default.
4. Highlight it in the "Selected" listbox, then click on the "<" button to
remove it from the list.
5. Click the "OK" button,
6. Now go to the Client key in the Configuration string and repeat steps 2>5
then apply your changes by clicking on the Apply button
(button with a red "!" on it")
or
by clicking "Settings", "Apply All" in the menu.
7. Close the Control Centre, stop the engine, and kill all open W3DBSMGR processes in the task manager (Ctrl-Alt-Del once!).
8. Then re-start it (it needs to be running on the machine with the data, the Gateway machine)
Do you have a Startup shortcut to start the pervasive engine?
Try going to Windows Explorer, Drag and Drop or Copy and Paste the file C:\Pvsw\Bin\W3DBSMGR.EXE into your Windows start up folder as a ShortCut, via either your Start Menu at the bottom left of your machine or if you know its exact location in Windows Explorer, do it that way.
Typically C:\WINDOWS\Start Menu\Programs\Startup for Windows 9X or ME.
When it is in your start up folder, Right click on it then select properties>Shortcut and where it says Target it should say;
C:\Pvsw\Bin\W3DBSMGR.EXE -BTRV
(You add the -BTRV) click apply then OK
Reboot Windows
Regards
CABC Support
support@cabc.co.uk
[This message has been edited by CABC Support (edited 25 April 2002).]
[This message has been edited by CABC Support (edited 25 April 2002).]