When creating installers with multiple file associations, the "File Associations" screen in the installer (which allows the user to select/deselect which extensions to associate with the application being installed) appears in the Windows installer created, but does not appear in the Unix shell installer. This means all file associations are made without the user getting to choose.
Is there a way to force the appearance of the file associations screen?
This is indeed a bug in install4j, it will be fixed in 8.0.3, please contact support#ej-technologies.com to get a build where this is already fixed.
Related
I am in the process of updating our currently existing Chrome distribution so that when a user downloads a .pdf file, the file is opened automatically.
As a first step, I was able to prevent Chrome from opening the pdf in its internal pdf viewer and could do a registry entry by using AlwaysOpenPdfExternally. This way it was downloading the file immediately and not opening it in the Chrome viewer.
I'd like to use Adobe to view the file automatically after download.
Unfortunately I was not able to find a registry entry. Nor was I able to find a GPO entry to be changed for Chrome.
I had found the following PowerShell script to be started upon logon of the user. However, testing it did not give me the result I was looking for.
The given entry extensions_to_open was not existing even after starting the script.
The current version of Chrome used is 66.255.
I would be happy for any help.
Edit: I am able to get the file to be opened automatically by inserting the given line here:
Is there any way to programatically force "Always open files of this type" for a specific file type in Chrome?
however, I am unsure of how to distribute the line of code into every PC in my network.
Edit: Chrome offers Group Policy Templates which should be importet into the active directory of your Windows Server. Once imported into your GPO, Chrome offers the setting: "Always open Pdf files externally". Once you check this feature, file should not automatically open in the internal PDF viewer.
See second edit: import the latest group policy templates into the GPO (will be stored on the active directory). After that, go into the GPO policies for "Google Chrome" and check the feature "Always open PDF files externally".
In our "Installation Location" screen we have switched off "Suggest application directory" because it was appending a suffix to the directory users chose (not sure where the suffix came from as different people where seeing different things with the same build).
I wanted to know what kind of impact this change could have as the screen help says: "[...] only switch this off if you substitute a different installation directory in the screen validation".
We don't actually substitute the directory in the screen validation, however before showing the Welcome screen we do run an action to set an initial installation directory our users can override.
By default, the "Installation location" screen appends the installation directory name that you have configured in the media wizard.
If you turn off “Suggest application directory”, and a user selects "C:\Program Files" as the installation directory, the application will be directly installed into that directory, which is not desirable.
I have to print out one of my projects and the built-in print function of Eclipse isn't doing a good job at all. Font, font size, page border etc..
Does anyone know a plug-in or tool to print out my whole project easily? Maybe with some formatting options on it?
After a little bit google, I've encountered enscript but its an Linux tool and unfortunately I'm on a Windows machine.
Regards
The most recent plugin about printing and printing preview is:
swt-paperclips
a simple, light weight, extensible Java printing plug-in for SWT.
PaperClips hides the complexity of laying out and rendering documents on the printer, helping you focus on what to print instead of how to print it.
In a nutshell, PaperClips provides an assortment of document "building blocks," which you can tweak and combine to form a custom document.
The assembled document is then sent to PaperClips for printing.
PaperClips includes support for printing text, images, borders, headers and footers, column layouts and grid layouts, to name a few. It can also be extended with your own printable classes.
Here in an example in this article:
alt text http://www.schmeeky.co.uk/assets/drgalleries/19/thumb_print_dialog.png
Eclipse does a terrible job printing on Windows. But there is an excellent version of Enscript that works for Windows and does great printouts. You have to set it up as an external tool which is a bit of a bear, but once it's setup it works well.This how I installed it on XP.
Download and install Enscript for Windows
http://gnuwin32.sourceforge.net/downlinks/enscript-src.php
Create an external tool for running Enscript in Eclipse
Goto Eclipse, Run -> Configure External Tools. Add a tool (icon looks lie a miniature document with +)
Name it "Run Enscript". Configure as follows:
Main Tab
Location : browse to the Enscript executable. Should be in:
C:\Program Files\GnuWin32\bin\enscript.exe
Working directory: leave empty
Arguments:
--header=${resource_name} -p "${workspace_loc}\${project_name}\print.ps" "${resource_loc}"
(These options will create a postscript file named print.ps at the top level of your project from the currently selected window.)
Build Tab
Clear "Build before launch" or it will try to rebuild your project each time you print..
Send the file to the printer
You need to find a way to send the file to the printer. Several utilities to do that, but since I had a postscript capable printer all I had to do is to share it under Windows, and copy the file to the share name. I automated this by adding another external tool, named "send ps file to printer"
Main Tab
Location: C:\WINDOWS\system32\cmd.exe
Working directory: leave empty
Arguments:
/c copy "${workspace_loc}\${project_name}\print.ps" \\your-machine-name-here\your-printer-share-name-here
(this will pick up the file we just created and send it to the printer)
Build Tab
Clear "Build before launch"
Voila, two clicks to run the tools one after the other and it prints clean. You can configure it further by adding Enscript options to the argument line. Here are a few useful ones:
- specify a slightly smaller font size (default is 10):
-f Courier8
- truncate lines instead of wrapping: -c
- precede line with its line number: -C
I installed Eclipse and am having some trouble relating to denied user permissions.
I am working on Vista inside a Windows domain. My user account is very restricted. My boss needs to grant administrator permission any time I install any application or establish a new network connection through the firewall.
Here are some of the problems that have occurred:
At Eclipse startup, Vista asks every time if I really want to run it. It doesn't remember my decision.
Eclipse doesn't remember my default workspace.
I installed the BIRT plugin. After a second restart it doesn't work anymore. The BIRT perspective does not run fine.
What permissions do I need to run Eclipse on Windows?
This problem occurs when you host the Eclipse application within a directory that is protected by the Vista or Windows 7 operating system. For example, %ProgramFiles%, %ProgramFiles(x86)%, or %ProgramW6432%. Unfortunately, for all of Eclipse's maturity, it still doesn't entirely restrict its per-user activities to the Windows operating system's user space.
If you don't care where your Eclipse application resides, or you don't have admin rights on your system, try moving the Eclipse application to a directory that is not protected by the Windows operating system.
If you have admin rights on your system, and want your Eclipse application to be hosted in one of Window's protected directories, you must make the directory writable to users. This will allow the proper operation of the Eclipse application, but be warned that it will also allow users to directly modify files within the Eclipse application directory. You can reduce this risk by making the directory writable to only the specific accounts that you choose.
Note that by performing either of the above solutions, it will not be necessary to run the Eclipse application with the "Run as Administrator" option.
To make the Eclipse application directory writable by users:
Right click on the Eclipse application directory within Windows Explorer.
Select "Properties".
Click the "Security" tab.
Click the "Edit..." button to change security permissions for the Eclipse folder.
If you want only specific user accounts to be able to write to the Eclipse application directory, click the "Add..." button to allow those accounts to appear within the "Group or user names" list.
One at a time, select each account to be granted write access to the Eclipse application directory, and then click the checkbox for "Modify / Allow" such that the checkbox is checked.
Conversely, if you want to allow all system users to be able to use Eclipse properly, select the "Users (YourComputerName\Users)" group from the "Group or user names" list, and then click the checkbox for "Modify / Allow" such that the checkbox is checked.
After all appropriate users have been given write access to the Eclipse application directory, click "OK". You should now be able to run Eclipse without issue.
tharkun's answer is sort of correct but I just wanted to post a "more correct" answer for anyone else who finds this question in the future.
For some reason, Eclipse needs administrator privileges in Windows 7 and Windows Vista machines. To do this one time, right-click the Eclipse executable or shortcut and click "Run as administrator"; to make it permanent, go to properties, the compatibility tab, and check the "Run this program as an administrator" box.
Despite tharkun's post, perhaps he forgot, Eclipse doesn't have an installer; you simply unzip it. There is no reinstallation necessary. If you run Eclipse normally and find something wrong, and just discovered this answer, you can safely run Eclipse as administrator from now on and nothing will be broken as a result of you not having run as administrator up until this point.
The problems with Eclipse that require administrator mode do not show up immediately, but for example if you check for updates with Eclipse running in non-administrator mode, Eclipse will claim that there are no update sites available. Also some GUI features will have problems.
These problems are likely caused by some of the advanced UAC features meant to protect your system, such as UAC Virtualization. Eclipse can (and hopefully will) be fixed to write only to user space and "play nice" with other Windows applications, but for now we have to simply run it as administrator and trust that it's not taking advantage of the added privileges.
As a sidenote, I just spent several hours trying to figure out how to get Eclipse to write inside the %AppData% directory, in hopes that it would solve this problem and allow Eclipse to be run in user mode, but I could not get Eclipse to honor anything I tried. Oh well...
eclipse require write permission to app folder
it has to be in a folder with user write permission, f.e. %localappdata%\Eclipse. if u place it in %programfiles%\Eclipse it can't write to config files or plugins
the app has no installer. it stores config files in the app folder by default. the official install path is "c:\eclipse" and they forgot to mention that write permission is required
https://wiki.eclipse.org/Eclipse/Installation
Decompress this file into the directory of your choice (e.g. "c:\eclipse" on Windows) and ensure you have full Read and Execute permissions.
I have an application written using VS2005 in C# targeting the Compact Framework 2.0 SP2. As part of the solution, I have CAB deploy project which deploys to the device without a problem. What I can't do is create a shortcut to my application on the devices desktop.
I have spent several hours reading various bits of documentation (why is the search at the MSDN site so bad?), followed the instructions but no joy.
What I've done is:
Add the "Windows Folder" node to the File System
Created a folder underneath that named "Desktop"
Created a shortcut to the Applications Primary Output and placed that in the "Desktop" folder
What am I missing?
A bit late but maybe this will help somebody like me who searched for this issue, I solved the problem like this:
I added a custom folder on the root node (File System on Local Machine) and called it %CE3%.
That is the shortcut for \Windows\Desktop.
I added my shortcut (right click create new shortcut) and gave it a name.
That's it, then I build!
When analysing the Shortcuts section in the inf generated, it looked good.
[Shortcuts]
"ShortCutName",0,"MyApp.exe","%CE3%"
And when I deployed and it worked perfectly!
I'm using VS2008 and deploy on windows CE 5.0
Here is a list of shortcuts: windows CE shortcuts
A Windows CE shortcut (CE of any version or flavor, including WinMo) uses a ASCII-text based file. They are in the form:
{XX}#{PATH}
Where:
XX = the number of the characters in the path, to include the number a # sign
PATH = fully qualified path to the file to run
For example:
20#\Windows\calc.exe
The other option is to use the CEShortcuts section of the INF file used to generate your CAB.
In the [DefaultInstall] section of the INF, set the CEShortcuts to a section name of your choice (something like "Shortcuts"), then add that section with your shortcut descriptor. MSDN details it here.
MSDN also has an article on creating a deployment project to generate the cab (available here), but in all honesty, the project capabilities are limited and IMO the tool just generally sucks. To this day we still use direct calls to CABWIZ (which also sucks, but it's our only choice) with hand-written INF files.
I had this same problem and found a simple solution, if anyone still needs this.
Instead of adding a windows special folder, just add a custom folder named Windows, then a folder within it named Desktop, and put the shortcut there.
This worked for me.
The Simplest way is to go into the Application folder in Cab Project(setup), right click on your EXE Program(Application exe that you want to make shortcut for) and chose "Create Shortcut to" and move that file to any folder you want such as "Start Menu Folder"
Mitch: create the LNK file as before, but give it a name like "shortcut.lnkx" (note the "x" on the end). You can then add it to the "Desktop" folder in your CAB project. Once the file is added, change the TargetName property to "shortcut.lnk" and compile. I think this will work.
Assuming that you use Windows Mobile (5.0 or 6.x) you could use that syntax to create a file as a shourtcut(*,lnk):
SHORTCUT = XX#"\Program Path..."?\Icon File Path...,-Icon Number
Where:
XX = Count of characters to be included in arguments after the Program Path to process.
Program Path = Target exe file location.
Icon File Path = If exe file does not contain an icon image or you want to use another, this is the location of the file containing the icon image.
Icon number = Index of icon image within the file, it starts with 0.
Ex: 86#"\Storage Card\Logical Sky CEdit\cedit.exe"?\Storage Card\Logical Sky CEdit\cedit.exe,-101
I had test it, and works fine.
1.Copy the file.
2.Go to desktop (or wherever you want to create the shortcut).
3.Right click on an empty space, click Paste Shortcut.
That's it.
Actually, this is pretty simple ! (Using VS 2008 and Smart Device CAB project)
1- In the solution explorer on VS, Go to your CAB project and right-click on it.
2- Go to View -> File System
3- Here, on the left column, right-click and "Add Special Folder"
4- Select Start Menu Folder for the shortcut folder
5- Go to the Application Folder just above
6- On the right column, right click on the Primary output and select "Create shortcut to bla bla bla"
7- Then you just have to move it to the start menu folder on the left and rename the File :)
OPTIONAL: You can even add fonts to the device using "Fonts folder" in the "Add Special Folder" menu !
Cheers
I assume that you're working with a "Smart Device CAB Project"? I don't think this project creates shortcuts in the correct manner for Windows CE 4.2. I think you can download an SDK from Microsoft that after installation will show you something like "Windows CE CAB Project" as a project option.
I think you can do this manually, though. A Windows CE shortcut is a file with a *.lnk extension, so if you want a shortcut labeled "My Application", create a text file on your PC named "My Application.lnk". The file's contents should be:
46#\Program Files\My
Application\MyApplication.exe (the # should be the full path length)
or whatever full path your application has on the Windows CE device.
In your CAB project, continue with adding the "Windows" folder and then the "Desktop" folder as you were. In the Desktop folder, right-click and add the LNK file that you created. You may have to soft-reset the device in order to have the shortcut show up after installation.