Cannot install VB6 on windows 2003, are they incompatible ?

HI guys,

I am trying to install Visual Basic for Windows Enterprise edition version 6.0 (thats the exact line on the CD!) on a windows server 2003, standard editon, SP1 installed. The setup does invoke, asks me licenes key, I am good till that point and after the next screen it throws an error saying "config.nt The system file is not suiotbale for running MS-DOS and Microsoft Windows Application". The title of this error window is "16 bit windows system".

Thats weird - windows 2003 server is not a 16 bit system!! :confused:

I am logged in as an administrator and have tried running the Setup.exe file with different compatibility modes too.

Any ideas ???


Thanks

Is the Windows 2003 a 64-bit version? If so I doubt VB6 can run on it.

Quote:

---

Originally Posted by MartinLiss

Is the Windows 2003 a 64-bit version? If so I doubt VB6 can run on it.

---

Hello Martinliss, its a 32 bit windows 2003.
what next ? :confused:

Sorry, no idea.

Using the same CD, can you do an install on an XP workstation machine?

i recently installed a copy VB6 onto windows server 2003, the install ran fine the problems came when i attempted to run VB6, as server 2003 is missing several files required for it to run which aren't in the install package i had to download each missing component from the internet.

anyway back on track:

Quote:

---

If you try to start or install an MS-DOS-based or a 16-bit Windows-based program on your Windows XP-based computer, you may receive an error message that is similar to one of the following:

16-bit MS-DOS Subsystem path to the program that you are trying to start or install C:\Windows\System32\config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

You may encounter to other similar error messages, but with different file names config.nt and Autoexec.nt. This issue may occur if one or more of the following files are missing or damaged:

Config.nt
Autoexec.nt
Command.com

---

VB6 is neither MS-DOS-based nor 16-bit so how does that quite apply?

Because the error suggests otherwise...

Download the file from here here.

Place the file in your System32 folder and attempt the install again.

Quote:

---

Originally Posted by vb help

Because the error suggests otherwise....

---

VB stopped being 16-bit back with VB5 (or maybe even 4), and it's obvious it's not DOS-based.

I’m not disagreeing with you however unless he’s giving us the wrong error message or the wrong VB version then I must presume that although VB6 doesn't need the Config.nt to run it must need it to carry out the installation either way that should be the resolution to that error message.

Quote:

---

Originally Posted by vb help

...unless he’s giving us the wrong error message....

---

Not necessarily. I have no idea what the problem is but the reason I originally asked about 64-bit is because since VB6 was written before there were any 64-bit operating systems, that the message about "16 bit windows system" might be the default when the OS isn't 32-bit.

Having said that, I'm dropping out of this conversation since I don't think I can help.

Quote:

---

Originally Posted by Hack

Using the same CD, can you do an install on an XP workstation machine?

---

Yes the same CD lets me install on XP.

Quote:

---

Originally Posted by vb help

Because the error suggests otherwise...

Download the file from here here.

Place the file in your System32 folder and attempt the install again.

---

Thanks for the help buddy, but this didnt get things going either...

Quote:

---

but this didnt get things going either...

---

thought that might happen as it's the xp version, try this taken from Microsoft Support

Quote:

---

1. Insert the Windows Server 2003 CD or the Windows 2000 Server CD into the CD drive.
2. Click Start, click Run, type cmd, and then click OK.
3. Type the following commands, and press ENTER after each command:
expand D:\i386\config.nt_ %systemroot%\system32\config.nt

expand D:\i386\autoexec.nt_ %systemroot%\system32\autoexec.nt

expand D:\i386\command.co_ %systemroot%\system32\command.com

exit
Note The description of this procedure assumes that your CD drive letter is D. If your CD drive letter is not D, substitute the correct drive letter.
4. Start or install the program. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to the next step.
5. Start Notepad, and then type the following commands.

Note The Command.com file is not edited or created in the following process. Because of this, you may have to expand the file from your CD-ROM. See step 16 for instructions on how to do this.


dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

6. On the File menu, click Save As.
7. In the File Name box, type Config.nt, and then click Save. Close the Config.nt file.
8. On the File menu, click New.
9. In the new blank document, type the following entries.


@echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

10. On the File menu, click Save As.
11. In the File Name box, type Autoexec.nt, and then click Save. Close the Autoexec.nt file.
12. Start Windows Explorer. Locate the Config.nt file, right-click the Config.nt file, and then click Copy.
13. Right-click the %systemroot%\System32 folder, and then click Paste.
14. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and then click Copy.
15. Right-click the %systemroot%\System32 folder, and then click Paste.
16. Expand the Command.com file from the Windows Server 2003 or the Windows 2000 Server CD-ROM. To do this, follow these steps:
Click Start, click Run, type cmd, and then click OK.
expand cd-rom:\i386\command.co_ drive_letter:\system_root\system32\command.com

exit

17. Verify the existence of the folder to which the TEMP and TMP user environment variables are mapped. To do this, follow these steps:
a. Click Start, click Run, type sysdm.cpl in the Open box, and then click OK.
b. In the System Properties dialog box, click the Advanced tab, and then click Environment Variables.
c. In the User variables for UserName section, locate the TEMP and TMP variables. They are listed in the Variable column.
d. For the TEMP and TMP variables, note the corresponding folder that is listed in the Value column.
e. Start Windows Explorer. To do this, click Start, click Run, type explorer in the Open box, and then click OK.
f. Locate the folder that is specified for the TEMP and TMP variables. Make sure that this folder exists.

Note To locate the folder, you may have to turn on the feature that shows hidden files and folders. To do this, follow these steps:
1. On the Tools menu, click Folder Options, and then click the View tab.
Under Hidden files and folders, click Show hidden files and folders, and then 2. click OK.
Restart your computer.

APPLIES TO
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows 2000 Server

---

i must be missing something here, but why would you want to run vb on a 2003 server?
should be on a workstation

Quote:

---

Originally Posted by westconn1

i must be missing something here, but why would you want to run vb on a 2003 server?
should be on a workstation

---

Apparently the economic recession is to be blamed. We have some new work in VB at my office and the company wants to use existing infrastructure wherever possible (read no money would be spent on new machines untill you squeeze to death every CPU cycle in existing machines!)

Also when you want to create applications to be used with the Active Directory it's a bonus to have a laptop with server 2003 and VB installed for testing.