FiveTech Software tech support forums

... eliminates the discovery process and will resolves 6420 errors. For a direct connection, configure the IP_PORT on the server in the ADS.CFG for Netware or in the Advantage Configuration Utility for Windows 2000/NT. Then, specify the IP address and port in the ADS.INI file. ADS.INI example [MYSERVER] ...

... eliminates the discovery process and will resolves 6420 errors. For a direct connection, configure the IP_PORT on the server in the ADS.CFG for Netware or in the Advantage Configuration Utility for Windows 2000/NT. Then, specify the IP address and port in the ADS.INI file. ADS.INI example [MYSERVER] ...

... eliminates the discovery process and will resolves 6420 errors. For a direct connection, configure the IP_PORT on the server in the ADS.CFG for Netware or in the Advantage Configuration Utility for Windows 2000/NT. Then, specify the IP address and port in the ADS.INI file. ADS.INI example [MYSERVER] ...

... Advantage Database Server processes data requests and returns the information to the network clients. The Advantage Database Server supports the NetWare, Windows, and Linux operating systems. The Advantage Database Server for NetWare is implemented as a NetWare Loadable Module (NLM). The Advantage ...

... If an error sequence in consecutive records in the error log exists with error codes 16, 128, and 7008 (for the Advantage Database Server for NetWare), or 32 and 7008 (for the Advantage Database Server for Windows), this indicates that a non-Advantage application already has the file open, ...

... the index. these problems happen very rarely, if network devices are certified happened with the old clipper + blinker over coaxial cables and Netware It would be nice an engine light and free But Just a question to Tim: is it true that ADS only write and read is directly from client?

Norberto, many years ago when I used Clipper, ntx index files, ms-dos and Netware server and coaxial cables based lan. I had many problems like corruption detected of ntx and dbf too. I informed about ADS. If I remember correctly browsing, reading of record contens ...

the Netware login script used to set an evironment variable "UserName" Great idea!!! I even didn't think about it!!! It's all work well. There are two the same variables I need: NWUSERNAME and USERLOGINNAME. Also ...

There is a netware 3rd party 'legacy' clipper and 32 bit .dll from Blinker ( blinkink.com ) called 'NovLib' .. it is specifically for Novell networks. It is a legacy product and did work 'somewhat' in a NDS\eDir environment. When ...

Sorry it has been a while since we moved from Netware. I would have to do some more checking to find out why the netname() function is not working right. Here is another idea, I remember the Netware login script used to set an evironment variable ...

You have to have either have NETBIOS.SYS for Netware Requester

I have NETBIOS.SYS in windows\system32\drivers

in Windows have netbeui turned on.

Do you mean this flag in network connection properties?

Netname() requires netbios to be turned on. You have to have either have NETBIOS.SYS for Netware Requester or in Windows have netbeui turned on.

Hello, Does anybody know the answers on this two questions: 1. How can I get my current login in Novell Netware ( something like function WNetGetUser() for Win ) For clipper there was a lib called "netto", which has all functions especially for novell. It should be ...

Wouldn't the user name be the same? If you are not using the integrated log in then how about netbios.sys. Novell NetWare Requester provides a NetBIOS driver (NETBIOS.SYS) that emulates the NetBIOS protocol so netname( .t. ) should return correct network name.

Hello, Anser!
Thank you, but I can't find the command "WhoAmi" in FWH, xHarbour or OS Windows and Novell NetWare
May be it's only for Linux...
Have you some example of usage this command?