After copying a control placed on a form in the VB 6.0 IDE you receive the following error message when you attempt to run the program.
The program will not compile correctly even after the VB control that you copied has been deleted from the form.
This seems to be a bug in the VB 6.0 IDE. Remember this?
It asked you if you wanted to place the control into an array so that multiple controls named ‘Command1’ in this case could be referenced from a common name i.e. Command1(0), Command1(1), Command1(2) etc.
Very occasionally the VB IDE gets this wrong, attempting to reference a control variable as an array variable. This in turn leads to non-compliable code and no clear way to get out of the problem.
The fix is to prevent the VB IDE from trying to treat the original variable as an array by removing its index parameter.
- Delete or rename the duplicate named control
- Note the name of the control in the error message
- Save your project and exit VB
- Open the location of your .vpb (Visual Basic Project) file
- Locate the .frm file (form) that your control appears in amongst the list of files
- Open notepad and drag and drop the .frm file into its window so that you can see the underlying code-behind the form
- Search the file for the name of the control named in the error message
- Beneath it you should find a parameter list associated with the control. Locate and delete the line “Index” line as highlighted below
- Save and exit notepad and restart the IDE
Or, if the control exposes it, clear the value of ‘index’ on the properties explorer in the IDE.
- Windows XP Professional, SP2, SP3
- Windows Server 2003 SP1, SP2
When you attempt to run the Remote Installation Service (RIS) image preparation tool (RiPrep.exe) on a Windows XP or Windows Server 2003 system with the latest service pack you receive the following error message.
This error is generated despite having the latest build of RIPrep.exe from Windows 2000 Server SP4 – 5.0.2195.6685 at the time of writing. If you do not have this build of RIPrep you should obtain the current version from Service Pack 4 and update your RIS host to SP4 before continuing.
Microsoft’s XP SP2 secure code initiative and several years worth of code development has seen some fundamental changes in the standard setup api used on XP and Server 2003 systems. The problem is caused quite obviously by the lack of the entry point UnmapAndCloseFile in the setupapi.dll.
Very simply, you need to give riprep.exe access to a version of the dll with that entry point.
- Go to your Windows 2000 Remote Installation Server (ensure that it is SP4)
- Navigate to %SystemRoot%\System32
- Copy the file setupapi.dll into the <RISPath>\Admin\i386 folder
- setupapi.dll from Windows 2000 SP4 (version 5.0.2195.6622 as of writing) will now be next to the riprep.exe
- When you run RIPrep from the \\<server>\REMINST\Admin\i386 folder, the version of setupapi.dll in this folder will be used as a higher precedent to the version in the Windows XP or Windows Server 2003 %SystemRoot%\System32 folder, and RIPrep will be able to load correctly.
- Windows 2000
- Windows XP
- Windows Server 2003
When you attempt to slipstream a service pack into your Windows installation media you receive the following error message:
The Service Pack cannot be integrated into a destination that also has integrated Software Updates.
Consult the Service Pack documentation for more details about supported integration scenarios.
The slipstream integration process subsequently terminates without making changes to your deployment share.
The redistributable media that you are using has been slipstreamed using QFE updates (not just Service Pack updates but regular patches as well). The Windows Service Pack integrator is unable to adapt to having updates in the install process which would clearly conflict with the new Service Pack version itself (for example you could not apply a RTM or SP1 update to an SP2 install).
To fix the problem, ideally you should attempt to locate a clean installation medium, however if all you have is the QFE integrated disc – such as the ones that Dell ship with many of their own systems.- the following steps will get you around the error.
- Open your Deployment share
- Open the i386 folder
- Delete the directory called:
- Locate and open the .inf file called:
- For every .exe referenced in the [SetupHotfixesToRun] section, perform a file search of the i386 directory for the file name (minus the .exe) e.g. Q306676.EXE search for Q306676
- Delete any files that come back as a result of the search
- Close SVCPACK.INF
- Delete SVCPACK.INF
You will now be able to slipstream integrate the Service Pack update.