Crashing

Started by randem, September 30, 2007, 11:29:36 AM

Previous topic - Next topic

mitty

Well, here's what I see.  I just put the patch on my desktop and tried to execute it.

Randem

mitty,
 
Try this version (7.2 Build 3)and let me know what you see

Randem

Glad InnoScript has worked for you.
 
Yes, We will let you know. You are automatically on the InnoScript Update Email list.

mitty

It's well worth the fifteen bucks even if it is a little warty.  I already have the setup package that I needed.  Without your app it would have taken much longer to figure out Inno Setup.
 
Pls let me know when the updated app is available.

Randem

Ok, We will be working on new screen resolution for many more resolutions. But for now 1280x768 and 1280x800 are the best for rendering.

mitty

Update:
 
1) Accelerator keys are there, but when the buttons are not rendered, the keys don't work.  Too bad.
 
2) Running the app at 1280x768 gets me the buttons although my flat panel squishes the width of the screen and everything is very tough to read.  It only works, however, if I switch to this resolution before loading the app.  If loaded, the app apparently does not process the windows messages associated with screen resizing.

mitty

Renaming the ini doesn't work at all.  It makes the entire screen area of the tabbed control stay blank even after the pjt is loaded.
 
I did try the app on the P1610 native screen (I use 1280 x 1024 when it is docked) and at 1280 x 768 the control renders properly with the buttons at the bottom.  Too bad you didn't provide accelerator keys for those hidden buttons!
 
I have attached the ini.

Randem

Also InnoScript was tested on a resolution of 1280x800 and you are using 1280x1024. Our resolution doesn't go that high so If renaming the InnoScript.ini file doesn't work I will have to test on a 1280x1024 system.

Randem

Here is what the screen is supposed to look like...

Randem

Rename the InnoScript.ini file then re-run InnoScript to see if that helps.
 
As for the file from the systems folder. Both applications explain in detail why you should not use those files and what to do if you are going to use the files from the system folder. You are suppose to copy those files (after researching them) to another folder and re-direct InnoScript to search for the files there by adding the path to the search area.
 
The Add Files and Add Folders tabs both have buttons on the bottom to allow input. Since your screen is not displaying properly that is why you do not see the buttons.

mitty

OK, redownloaded, paid the $15 and things are looking promising.  I got Inno Setup to run through to a plausible-looking installation program though I did not run it to completion.
 
But
 
My app apparently wants mscoree.dll which is only available in c:windowssystem32.  Your program and Inno Setup are both very unhappy with this.  Do I put a copy in my app directory, just delete the reference, or what?
 
8 - Add any additional files or folders ...
 
How?  Neither the Add Files nor the Add Folders accepts input.  I can click to get a white select box outline on the first line but cannot figure out how to launch a file dialog and the box will not accept typing.
 
And ... InnoScript is still not displaying properly.  Same as the screen shot I posted, the bottom quarter of the form is not rendering even though the bottom ribbon appears.

Randem

Yes, We could do a refund if you don't use it after the trial period of 5 days.

mitty


Randem

mitty,
 
SOrry, there is no way to reset the trial period. You would need to install on another machine for the trial period.

mitty

>4 - Did this happen the first time you started InnoScript?6 - Why did you remove the VB Runtime File Location. 7 - Did you get any installation errors.
You had no extension (.iss) in the script dropdown box