I'm having a problem with installscript, and I'm trying to get the OS Version and detect if it's windows 10.
The Key that I'm trying to get is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\[CurrentVersion]
Using regedit, Windows 10 has the value 6.3 there. The same has Windows 8.1 and Windows 2012.
But, if I use WINVER on commandline, I get 10.0. How can this be?
Instead of reading the value CurrentVersion, read the new values CurrentMajorVersionNumber (which is 10) and CurrentMinorVersionNumber (which is currently 0) under Windows 10. Those 2 keys are new in Windows 10 to detect Windows Version from Registry.
At runtime, you need to have your application manifested correctly in order to get the right value from the version checking APIs; see this MSDN topic on how to set it up, and then you can use the Version Helper APIs to get the right value. I don't know how much of that you can do within your installer project though.
Related
Earlier in Windows XP, Our projects Uses the following code to change the system locale in Windows XP.
driveStr.Format("RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection %.8x 128 %s\\inf\\intl.inf", lgid, getenv("windir"));
Now we migrated the project to Windows 7, Whenever we try to change the language using above format, Application crashes. Later figured it out that the file Intl.inf which used in Windows XP is not part of the Windows 7 anymore which causes the application to crash.
Please let me know, Is there any way to change the system locale on Windows 7 using Command prompt
If you are using mshtml as an embedded browser in Windows and want it to render in the latest installed render model (i.e. using the latest installed IE) you can use the following registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
And add your program name and the number "0x0". Normally you set it to a value to correspond to a specific IE version, but in my program I always want to use the latest installed version.
In Windows 10 this does not work anymore. Setting "0x0" then crashes the application if rendering a local page or gives a blank page for an Internet page. The "0x0" setting works fine with IE6-11 and Windows XP to Win 8.1.
Not setting anything gives either IE6 quirk mode or IE7 quirk mode. Setting it to "11001" in Windows 10 also works.
Is this a bug in Windows 10? (I know that the "0x0" setting is not documented...)
How do I get the latest installed Browser Emulation no matter what Windows version or IE I have installed?
P.s.
If an upgraded IE is installed after my application I still want the latest version.
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
Moving from XP to Windows 7 with client side.
Running into a couple issues with Sybase 15.
1) "Interactive SQL" - many widgets in ie options are defective or missing
2) When running simple query get Swing/AVT widget exception error.
Anyone ran into or worked thru any issues moving to 7?
Other versions of the Windows app, but not 7. As you may be aware 7 is only slightly more reliable than Vista.
Those messages are classically due to (a) Sybase Client (SybaseCentral; InteractiveSQL, the GUI utilities) all using the Java VM and (b) that not being successfuly installed.
Get the Sybase Client CD, and install again. Do not Customise, use the Default installation options. Watch the progress for errors. Ensure the JVM installation succeeds. You may have to retrieve any missing files from the Windows 7 CD.
Otherwise open a Support Case.
we have a setup developed in installshield vr 6.3. it is a self extractable single setup. it work fine in most on most of the Windows version but on Windows server 2003 64bit in Execution mode when doing RD it return user windows directory against WINDIR i.e. c:\documents & settings\fcuser\windows instead of C:\Windows. According to http://support.microsoft.com/?kbid=186499 it should work fine when i change the compatibility bit of Setup but it didn't. i tried changing compatibility bit of these key too (INSTRUN, SETUP and SETUP1 ) but it didn't work either. but when i when i run the setup within the self extractable by extracting it work fine.
InstallShield 6.3 is 10 years old, released when Windows 2000 had just come out. There were no 64-bit Windows OSes at that time. I'm not surprised you're having trouble. You really should think about using a modern version of InstallShield, or migrate to something like Wix/NSIS if upgrading is not financially possible.
As I work-around to using WINDIR, you could try getting this Registry value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRoot
Or try to get the value of this environment variable:
%SYSTEMROOT%