Win2000 service / Arev FS1019 (Network Product)
At 17 JUN 2002 12:14:17AM Bob Watson wrote:
We converted out server from Novell to Win2000 and installed the win2000 service.
We have WIN NT workstations.
We are using pure TCP/IP
The system user has all rights to everything
The revparam says TcpIPPort=777
OI works fine
Arev gives the FS1019 error
What is the problem pleaase?
Bob Watson
At 17 JUN 2002 08:50AM joed wrote:
Bob;
Have you changed the AREV driver to the All Networks Thunk drive.
Joe Doscher
Rev. Tech.upport
At 18 JUN 2002 09:16PM Bob Watson wrote:
Ok - I tried the All Networks Thunk driver and it certainly changed the behaviour - now it tries to load and GPF's the machine with an access error on NTDVM - have you come across this?
Thanks
Bob Watson
At 19 JUN 2002 09:25AM joed wrote:
Hi Bob;
No I have not come across a GPF and NTVDM. I did a search on the web, used google, and came up with the below:
GPF
Short for General Protection Fault, a computer condition that causes a Windows application to crash. The most common cause of a GPF is two applications trying to use the same block of memory, or more specifically, one application trying to use memory assigned to another application.
NTVDM
The NT Virtual DOS Machine (a.k.a WOW, or Windows on Windows), is a Win16 subsystem that runs under Windows NT, which allows 16-bit applications to run as if they were being executed on a DOS machine, with that machine's multitasking and segmented memory model.
Because the system is multitasked 16-bit DOS and Windows applications cannot crash NT. However, 16-bit apps within a Win16 subsystem run the exact same way as they do on a DOS/Win 3.x machine; therefore, 16-bit apps within the subsystem can crash one another, or the subsystem. To prevent this, you can launch multiple WOW subsystems as long as your program does not communicate using shared memory.
Windows NT will not allow NTVDM to execute instructions that try to directly manipulate hardware or memory locations. As a result, some DOS and Windows 3.x applications (such as games) may not run under Windows NT.
We need some more info.
What is in the Revparam files?
What is in the Config.nt?
How is the short-cut setup?
Did you make the changes to the Revelation NT Service 2.1 with regedit on the server
Can you send us the windows.log and/or lh2.log; if not setup please setup and sent to us.
Have you tried logging in using either a win2k or xp?
If you want to do this over the phone please call 800-262-4747.
Joe Doscher
Rev. Tech. Support
At 20 JUN 2002 10:08PM Bob Watson wrote:
Joe
I've done some more experimentation
As soon as I change the driver to All Networks Thunk it becomes impossible to boot arev - I get the GPF (on all machines and for all accounts including sysprog). If I delete the revparam file I get the same result.
ServerOnly=1
TcpIpPort=777
files=200
How is the short-cut setup?
The shortcup is setup to call AREV /x /m4096. If I call arev from a command window I get the same thing. I can send you the complete pif but it's been working for years and is set up in the prescribed way.
]
We did - OI works fine.
Can you send us the windows.log and/or lh2.log; if not setup please setup and sent to us.
lh2.log doesn't get far
00.00.00.00 SN
Have you tried logging in using either a win2k or xp?
Sorry we have no machines with these op. systems.
Bob Watson
At 20 JUN 2002 10:21PM Pat McNerthney wrote:
Bob and Joe,
What are the exact size and date/time stamps of the dlls (yes, that's right, dlls) that got installed into your AREV subdirectories during the Win2K AREV client install?Pat
At 20 JUN 2002 11:04PM Bob Watson wrote:
Pat
23/11/01 09:58 90,112 APILH32.DLL
23/11/01 09:59 6,656 LHVDD.DLL
Bob Watson
At 21 JUN 2002 02:42PM Pat McNerthney wrote:
Bob,
Off hand, those look correct.The Thunking driver calls the 32-bit LHVDD.DLL, which in turns calls APILH32.DLL to perform the LH functions. Something is going terribly wrong in the thunking process to cause the GPF. One thought is to reinstall the AREV client, just to double check that everything is correct.If you can, configure the Win2K to use only named pipes, and then select the regular, non-thunking driver. Make sure that you can get this running first. Then, while still in the named pipe mode, switch to the thunking driver and see if that works. If that works next see if you can switch to tcp/ip mode.Another item to try that might provide a clue is try running an as clean as possible version of AREV on your local hard disk with the thunking driver. This "should" work just fine.Pat
At 26 JUN 2002 01:46AM Bob Watson wrote:
Pat
]
I'm trying to avoid this one at the moment since it would have to be done after hours with the network people in this building - I can't get my hands on the server. But if I have to I will.
Another item to try that might provide a clue is try running an as clean as possible version of AREV on your local hard disk with the thunking driver. This "should" work just fine.]]
I tried this after installing the driver again - same result.
It could be something to do with our autoexec.nt could it - here it is
REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe
REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir
REM Install DPMI support
lh %SystemRoot%\system32\dosx.exe
%SystemRoot%\system32\vipx.exe
%SystemRoot%\system32\vlmsup.exe
I tried remarking everything out but it still failed.
We are getting a win98 machine tomorrow - i'll try that.
Our arev system is only used for viewing and reporting now but I've had to ban everyone from using it - if they access a file it locks it out from everyone elses use in OI.
Bob Watson
At 08 JUL 2002 09:04PM Bob Watson wrote:
I wish to report that the All Network Thunk driver produces the same problem on a win 98 machine.