Printable View
More than half the time I build a web deployable install, I end up with error messages about files not being found or corrupt files despite the fact that there are no error messages during the upload process from SB 10 to the server.
Here's a video showing yet another example of an erroneous error message displayed by a SB install:
https://youtu.be/x_BfgiOUWow
I am using SB Version: 10.0.5452
Here's another issue that I encounter with the installer:
Attachment 4755
What kind of resolution and text size are you running? Windows handles the "resizing" of the dialogs, there is not any custom code involved.
Friedrich
Hello,
the upload process (Windows WiniNet) can only report error codes that your server returns back to the calling application. If your server returns 0 (no error) then there was no upload error.
Because SetupBuilder powers millions of web updates, it is highly unlikely that this is a bug. I assume it's a problem with the project (e.g. web configuration).
I would suggest to change inwordbible.com to www.inwordbible.com. Or send me your project file and I will fix the problem in your project for you. If you are interested, send it to support [at] lindersoft [dot] com. My test SetupBuilder installer downloaded your inword_00001.bin file without any problem on three different Win10 machines.
Friedrich
250% scaling on Windows 10-64 with LG Electronics 4K UHD IPS 32" Screen LCD Monitor (32MU99-W)
None of the other "pages" of the installer show any problems (other than the bottom hanging portions of letters get chopped off for the file names being downloaded and installed).
I had reboot the IIS server on which the *.bin files resided before I could get the installer to complete without an error.
Hello,
so the issue has been resolved now, correct? I think you had a typical (IIS) MIME problem here.
Friedrich
Hello,
please try it again with the default font type/site.
Does this make any difference?
Friedrich
I don't have any font called "MS Shell Dlg:8". My font is "Microsoft Sans Serif:9"
The default one (when you create a new project) is "MS Shell Dlg:8". Please delete your font and size and this will reset it.
Friedrich
I have done as you've instructed, but now the font is so small it is barely legible. See below:Quote:
Please delete your font and size and this will reset it.
Attachment 4760
Moreover, the gray rectangular area is still visible on the right side of the next to last window.Attachment 4761
Hello,
unfortunately, we can't reproduce this display issue on any of our machines :( Not even on machines with support for 4K. Would it be possible for you to send a screenshot from your display configuration (including scale factor, etc.)? I have opened a ticket for your issue.
UPDATE: we can reproduce this "Installation Progress Dialog" issue on a Surface Book now. Thank you for bringing this to our attention. Item in review.
Friedrich
Fixed in the latest internal SetupBuilder 2018 build! Thanks again for your help!
FIX : [SB#8-08291] Installer: Possible layout problems with the "Clarion Environment Detection" wizard and the "Installation Progress" dialog when the Windows custom scaling option was enabled to increase the size of fonts and icons on high-resolution displays.
Friedrich
What I had sent you yesterday in the way of a screen snapshot was taken from a Windows 10 machine connected to a Windows 2016 Server using Remote Terminal Services. The installer was being run on the Windows Server for testing purposed. I don't have Clarion, BTW.
Attachment 4767
So with a web install, why is the "Cancel" button disabled on the "Installer progress" dialog window?
That's fixed now. It was caused by a DS_FIXEDSYS style option in the progress dialog. The dialog box uses the SYSTEM_FIXED_FONT instead of the default SYSTEM_FONT in this case. This flag was there from the very beginning in 2003 (for more than 15 years) <g>.
Friedrich
It's a standard "Cancel" button from the underlying wizard. Cancel is not supported. We can add a "hide" option to hide the button, if you need it.
Friedrich
I was told last year that the minuscule font issue/problem on the installation dialog windows had been fixed. It was only after being told this issue had been fixed that I decided to take advantage of the renewal of my SB maintenance subscription. But now that I've actually tried your latest version of SB and created a new install package, I find that nothing has been fixed. You can see (or perhaps you'll need a magnifying glass to see) how the itsy bitsy font still appears on these dialogs.Attachment 4850Attachment 4851Attachment 4852
I think you are referring to the following:Quote:
Originally Posted by instrumentally
http://www.lindersoft.com/forums/sho...9491#post89491
FIX : [SB#8-08291] Installer: Possible layout problems with the "Clarion Environment Detection" wizard and the "Installation Progress" dialog when the Windows custom scaling option was enabled to increase the size of fonts and icons on high-resolution displays.
IMO, all the problems you reported in ticket [SB#8-08291] have been fixed (the rectangular gray region and the Cancel button pushed off the page).
Could you please post a screenshot from our SetupBuilder installer image running on your machine? For example, the "Welcome" dialog from this trial version installer:
http://www.lindersoft.com/downloads/sb10_dev_trial.exe
Attached is a screenshot from our machine with a 3840 resolution and 250% text size setting.
Friedrich
You can see a video of my system configuration in this video:
(URL removed)
I removed my original (system configuration) question because we have fixed the issues you reported in ticket [SB#8-08291] with SetupBuilder 2018 Version 10 Build (beta) 5995 (September 07, 2018).
http://www.lindersoft.com/forums/sho...9974#post89974
Friedrich
I just installed the latest 10.0.6124.0 version. I then recompiled my install package. I then ran the web deployment package. The result is that nothing has changed. The minuscule font issue that I showed you in screen snapshots and video still remains.
In fact, there is no "font issue" in SetupBuilder. The problem is specific to "your" machine.
Yeah, of course <g>. But here is why. The installer has to support all kinds of Windows versions, from Windows 95 up to Windows Server 2019. Windows is available in localized editions for many languages.
https://docs.microsoft.com/en-us/win...ms-shell-dlg-2
So the installer has to use the "MS Shell Dlg" font, which is not really a font but are aliased in the registry. You can set the font to something different by tweaking the registry. You can reset it to MS San Serif, or something like that.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\MS Shell Dlg
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\MS Shell Dlg 2
So in your case, (I think) you have set it to a very small font?! What you see is completely machine specific and is not an installer issue at all! SetupBuilder uses the "MS Shell Dlg" alias.
If you want, you can set the installer to a "fixed" font (e.g. "Microsoft Sans Serif"). This will solve your "MS Shell Dlg" redirection issue on your machine. But please note, the "MS Shell Dlg" alias is displayed correctly on 99.9% of all machines ;-)
Does this make sense?
Friedrich
BTW, for example, set it to the font that you have used in this installer (see attached screenshot). But from the technical point-of-view, it would be better to "fix" the font redirection on your machine so your compiled installer can make use of the correct font on your customer's machines.
Friedrich
Here are registry examples from our machines (Win10 and Server 2019). Just curious: what do you have in your registry?
Friedrich
]Quote:
So in your case, (I think) you have set it to a very small font?! What you see is completely machine specific
No. What you are seeing is the default setting for Windows Server 2016. I never changed the font in the Registry for the machine in question. Attached is the defaults for WinServer 2016.Attachment 4859
Yes.Quote:
Does this make sense?
Unfortunately, there is absolutely nothing we can do because it is definitely a machine specific issue.
So just set it to, say, "MS Sans Serif, 8" in your project, recompile and it will display fine again on your machine (like it did in the past; your screenshot from August 29, 2018; before I suggested to change it to the default "MS Shell Dlg"). But the recommended setting is "MS Shell Dlg" so Windows can choose the font on the target machine.
If you are interested, you can send me your setup.exe stub and I'll send a screenshot how it looks on our machines. We have about 50 different Windows machines and configurations.
Friedrich
Did you check the WOW6432 registry branch, too?
Friedrich