Changing from Novell IntraNetware to NT Server 4.0 (AREV Specific)
At 26 SEP 2000 11:29:24PM Vicki Bowes wrote:
In order to decommission the Novell server I was advised that :
1. All clients running DOS/WIN95/98 pc will have to be recofigured to run TCP/IP Protocol. Is the neccessary?
2. All rows in the AREV table TECH_STATIONS will need to be changed, as these records are keyed on the client pc's "station id", which for Novell server is the ID of the NIC. On NT Server the ID returned to AREV is the machine name. Is this True? do I need to change the tables? Is there another solution to this problem?
3. The CAPTURE utility program/script needs changing as the CAPTURE utility is not supported in NT.
Is there another alternative or utility ?
At 27 SEP 2000 07:45AM WinWin/Revelation Technical Support wrote:
Vicki-
1. Yes that is correct. The Linear Hash NT Service requires TCP/IP.
2. I'm not familiar with the TECH_STATIONS file. Is this application specific?
3. Instead of Capture you can try NET USE. The syntax would be NET USE LPT1: \\SERVER\PRINTER_NAME It is not as flexible as a capture command, but works.
Hope it helps-
Mike Ruane
At 27 SEP 2000 01:00PM Dave Harmacek wrote:
I converted a client over 15 months ago from Novell to NT…
1. All clients running DOS/WIN95/98 pc will have to be recofigured to run TCP/IP Protocol. Is the neccessary? — Why not? You will then need only one protocol on the network. I assume you will also have e-mail and browsing at each workstation.
2. All rows in the AREV table TECH_STATIONS will need to be changed, as these records are keyed on the client pc's "station id", which for Novell server is the ID of the NIC. On NT Server the ID returned to AREV is the machine name. Is this True? do I need to change the tables? Is there another solution to this problem? — I've never heard of TECH_STATIONS. This must be site specific. Not only do you get the machine name from NT, you may get also a session number. This makes the station id a multipart value with a "*" delimiter.
3. The CAPTURE utility program/script needs changing as the CAPTURE utility is not supported in NT.
Is there another alternative or utility ? — NET USE is the basis of control of NT printers. enter NET USE /? to see the syntax. Be sure to use the /D option or it will keep asking if you want to re-connect. You may also find that the print jobs don't close until your users exit from ARev. There is no AUTOENDCAP option in NT. So, I just submit another NET USE or place a call to the ARev routine SETPTR. If to LPT1 then it looks like CALL SETPTR( "LPT1":CHAR(0), 1)
where that is char(zero). This closes an existing job and keeps the network printer connected.
I suggest you also get the NT Service from RevSoft.
Dave
At 28 SEP 2000 09:43AM Don Miller - C3 Inc. wrote:
See Dave H's and WinWin's answers about differences between Netware and NT in terms of USERID or @STATION. In general, I've only used station-based ID's only for temp files (sorts, prints, etc.) since if a NIC card was changed then the station id in Novell would change anyway. I suppose you could save your self some grief by changing the Windows Machine-ID to the NIC card value contained in the Novell id. That way it would remain constant even if the card was changed and would work identically under NT as it does under Netware.
You can use little DOS batch files with the same name as the Netware command (CAPTURE, etc.) but instead, use the NT commands. Be sure to use an @ECHO OFF line to prevent garbage on the screen. The only problem is that with Netware you had to run CAPTURE through a SUSPEND action in AREV since CAPTURE is a memory pig. You could use PCPERFORM or whatever with a small batch file under NT.
HTH
Don Miller
C3 Inc.