Citrix bizarro? (AREV Specific)
At 02 APR 2002 03:42:14PM Warren wrote:
Citrix NT box. ARev 3.12 on Novell server with NLM.
From ARev TCL:
PC VER
-]MS-DOS Version 5.00.500
PC
F:\Arev312]VER
-]Microsoft Windows NT 4.0
???
Why? I need PC and PCPERFORM to think it is Windows 9x/NT/2000 for LFN support.
At 02 APR 2002 04:31PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
It's not just Citrix. All windows versions from NT and above have this problem.
When you PC from within ARev, you are running the COMMAND.COM shell and Windows will report this version. When you PC, VER will use CMD.EXE and report back that version.
You might want to use the SET command and parse the information from there or use Steve Smith's Get DOS environment as a string program.
World Leaders in all things RevSoft
At 02 APR 2002 05:42PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
We have a free utility for AREV users, ZZWINVER.EXE which produces a file ZZWINVER.TXT which contains the appropriate details of the Windows version. Similar functionality exists in S/Util32 for OI users. If you'd like a copy contact [email protected] with the email subject "ZZWINVER"
Steve
World Leaders in all things RevSoft
At 02 APR 2002 06:21PM Warren wrote:
Well the problem being we're exporting LDIF files for email directories…
…And Netscape's ldif import needs an extension of .ldif (case sensitive) or else it doesn't recognize it as a LDIF file.
OSWRITE/OSBWRITE only creates the file as X.LDI
Using the RT code snippet posted earlier for LFN in ARev doesn't seem to work properly across the different environments (Win98 workstations, Win2000 workstations, Citrix) or perhaps won't use lower case letters in the extension (don't exactly recall what the problem was with it).
Solution was to issue a PCPerform REN X.LDI *.ldif
However this doesn't work on NT because the PCPERFORM is shelling the command.com (DOS 5.00.500).
At 02 APR 2002 06:32PM Warren wrote:
Well, played around with various combos of START and CMD.EXE and got it working.
I'll just PCPEFORM the REN command and then the START CMD combo.
Getting too old and lazy to worry about elegant solutions.
At 02 APR 2002 06:44PM Warren wrote:
Take it back. START CMD.EXE REN not working…
At 02 APR 2002 06:52PM Victor Engel wrote:
I couldn't get that to work on NT either. There is another thread on this topic that lists a couple of other options. The thing that worked for me was to use start.exe from a Windows 95 machine.
At 02 APR 2002 07:34PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
We have developed, for AREV, a long filename interface. This lets you create/read/write/list/delete long filenames from AREV.
If you are interested in this functionality then [email protected]
World Leaders in all things RevSoft
At 03 APR 2002 12:44PM Warren wrote:
Is that the same [u] MAKELFN[/u] function that the long departed Eric Emu post some time ago?
If so, I tried it prior to the "REN" solution months ago. As I recall it (could be wrong) worked, but didn't work…perhaps changing to all caps. Again, Netscape insists that the extension be exactly ".ldif".
At 03 APR 2002 12:54PM Warren wrote:
Tried START.EXE from Windows 95b. No joy. I wonder if setver could fool NT? Probably not…
At 03 APR 2002 01:47PM Warren wrote:
Ok, problem with MAKELFN as previously posted is that it doesn't work on WinNT workstations.
Does the current version work on NT/2000/XP?
At 03 APR 2002 07:47PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
This version of makelfn is a different version to the one posted by Eric Emu. That version used an API call which was abandoned after Windows 95, and was an assembler object.
This version is a Windows 32 bit executable which was written on NT and tested on 2000.
World Leaders in all things RevSoft