This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- On wmware:SYSInfo return windows xp instead of windows server 2003
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2008
04:12 AM
On wmware:SYSInfo return windows xp instead of windows server 2003
I have a problem that happened only in InstallShield 2009. For unknown reason on wmware system, even thought the system is windows server 2003, when using the SYSINFO.nISOSL it return WINXP instead of windows server 2003. In InstallShield 2008 it doesn't happened,
Does someone saw this, have any ideas?
Thanks in advance. :confused:
Does someone saw this, have any ideas?
Thanks in advance. :confused:
(6) Replies
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2008
04:34 AM
Can you provide more details?
Is this a 32-bit or 64-bit parent system? What platform is the parent system?
Is the VMWare image OS a 32-bit or 64-bit OS? What version of 2003 Server and what SP?
Devin Ellingson
Software Developer
Accresso Software
Is this a 32-bit or 64-bit parent system? What platform is the parent system?
Is the VMWare image OS a 32-bit or 64-bit OS? What version of 2003 Server and what SP?
Devin Ellingson
Software Developer
Accresso Software
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2008
03:42 AM
The parent system is 32 bit and its windows server2003 service pack 2,
The wmware is 32 bit windows server 2003 service pack 1.
I made one mistake in my description, that it also happened with InstallShield 2008 but not with InstallShield 12, so until InstallShield 12 everything was fine.
The question is if there was a change in 2008 in this subject of how SYSINFO.nISOSL take it's values.
Thanx
The wmware is 32 bit windows server 2003 service pack 1.
I made one mistake in my description, that it also happened with InstallShield 2008 but not with InstallShield 12, so until InstallShield 12 everything was fine.
The question is if there was a change in 2008 in this subject of how SYSINFO.nISOSL take it's values.
Thanx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2008
05:37 AM
The parent system is 32 bit and its windows server2003 service pack 2,
The wmware is 32 bit windows server 2003 service pack 1.
I made one mistake in my description, that it also happened with InstallShield 2008 but not with InstallShield 12, so until InstallShield 12 everything was fine.
The question is if there was a change in 2008 in this subject of how SYSINFO.nISOSL take it's values.
Thanx
The wmware is 32 bit windows server 2003 service pack 1.
I made one mistake in my description, that it also happened with InstallShield 2008 but not with InstallShield 12, so until InstallShield 12 everything was fine.
The question is if there was a change in 2008 in this subject of how SYSINFO.nISOSL take it's values.
Thanx
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2008
02:03 PM
Is the Windows Server 2003 Image configured as a domain controller?
And yes there was a change in IS2008, from the release notes:
IOC-000046709
SYSINFO.WINNT.bWinXP now evaluates to TRUE as expected on Windows XP x64 systems. Previously, it evaluated to FALSE.
Devin Ellingson
Software Developer
Acresso Software
And yes there was a change in IS2008, from the release notes:
IOC-000046709
SYSINFO.WINNT.bWinXP now evaluates to TRUE as expected on Windows XP x64 systems. Previously, it evaluated to FALSE.
Devin Ellingson
Software Developer
Acresso Software
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 11, 2008
06:04 PM
I'm seeing this same issue. SYSINFO.WINNT.bWinServer2003 will evaluate to FALSE on a Windows 2003 Server configured as a domain controller.
Is there a fix or workaround for this?
Is there a fix or workaround for this?
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 15, 2008
06:14 AM
You can write script code to cover for this problem.
something like:
// Complete check for Windows Server 2003
if( SYSINFO.WINNT.bWinServer2003 ||
( SYSINFO.WINNT.bWinXP &&
SYSINFO.nWinMajor = 5 &&
SYSINFO.nWinMinor = 2 &&
SYSINFO.nOSProductType = VER_NT_DOMAIN_CONTROLLER ) ) then
MessageBox( "Server 2003", INFORMATION );
endif;
Devin Ellingson
Software Developer
Acresso Software
something like:
// Complete check for Windows Server 2003
if( SYSINFO.WINNT.bWinServer2003 ||
( SYSINFO.WINNT.bWinXP &&
SYSINFO.nWinMajor = 5 &&
SYSINFO.nWinMinor = 2 &&
SYSINFO.nOSProductType = VER_NT_DOMAIN_CONTROLLER ) ) then
MessageBox( "Server 2003", INFORMATION );
endif;
Devin Ellingson
Software Developer
Acresso Software
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)