WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Installation Licensing Setup
plus

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Keywords: 

Question:

I am installing WB 2001 as an upgrade to an older version that we bought with a server license.

When I run the "makeicon", which is supposed to install the icons in the start menu, the menu items are created with bad names. For example, the Winbatch icon points to compiler icon points to "WBat34i.exe" and the compiler icon points at "WBC-34i.exe". Neither of these files exist. I can edit the shortcuts by hand to point at the correct programs, but is there a way to get the installer to work correctly?

Answer:

Hmmmm. Those are the short versions of the file names. It uses short versions of the names when it detects that it cannot use long names.

Something strange is going on.

What kind of server do you have the Winbatch installed on?

For a test, enable write access to the server and see if it works better.

Question (cont'd):

The server files are on an NT4.0 server. I was installing onto a Windows 2000 workstation.

Answer:

When running the makeicon.exe file, are you running from a user account or an admin account.

Does the account you are using to run makeicon.exe have write access to the directory that the users win.ini file is in?

Please try this test

windir=DirWindows(0)
Message("Windows Directory",windir)
testfile=strcat(windir,"xxxtext.txt")
handle=FileOpen(testfile,"WRITE")
FileWrite(handle,"Test data")
FileClose(handle)
does the xxxtext.txt file show up in the windows directory. Where is the windows directory? Local or on a server? If a server, are long file names enabled for that server?

Question (cont'd):

  1. Running from an Admin account. (The same account that installed the software on the server.)
  2. The account has write access to the WINNT folder (which is the location of WIN.INI)
  3. I ran the test program (which crates a file in the sysdir) and the file was created.
  4. The windows directory is on the local machine.
  5. The server has long file names enabled. The winbatch install to the server created files with long file names.

Answer:

Time to pull out the heavy artillery.

Create a file named..

C:\wbsetup.dbg
obviously in the root of the c drive.

If a file c:\wbdebug.txt exists, delete it.

Run the makeicon.exe file.

A c:\wbdebug.txt file will be created.

Send me that file.

If you wish to poke at it yourself, there is a variable called UseLongNames that is somehow getting set to zero during the execution of he script. We need to figure out why it is gettng set to zero.

By looking at the wbdebug.txt file I can probably figure it out and then, depending on why it is getting set to zero, decide what to do next.


Article ID:   W14615
Filename:   MakeIcon and Server Install.txt
File Created: 2001:03:21:11:49:04
Last Updated: 2001:03:21:11:49:04