I have created a windows 7 gadget which works properly when i copy it to %LOCALAPPDATA%\Microsoft\Windows Sidebar\
but when i zip it and rename it to .gadget and then try to install .. install confirmation screens comes but gadget doesnt get install.
You can download my code from: http://reliablesoftwares.com/100thmilaadcountdown.zip (its a simple countdown)
I've been having the same problem, and I think found what I was doing wrong. I was zipping up the gadget in a folder with the gadget's name instead of just the gadget files.
I'm guessing that when you package your gadget, you're creating an archive from the gadget folder. Instead, you need to open the folder, and create the archive from the files themselves. In other words, the files (gadget.xml etc.) need to be in the top level of the archive.
That fixed it for me, hope it solves your problem too.
Related
On your PC how can you find the apk files that you install in BlueStacks? Someone suggested to go to C:\ProgramData\BlueStacks_bgp64\Engine\Android and check the .vdi files there with 7z. I did so, but I did not find anything in root.vdi. The system folders and files are there but no sign of installed apps. Data_0.vdi is a large file, I think the virtual system might be in that one, but if I open it in 7z, I can only see a large image file in it. It is 65GB in size, in spite of that I have no games and apps installed in Bluestacks, only Messenger. Should I mount that and browse it for the apks, or it is useless effort?
#Bencuri your are very near to solution. Just follow this steps to get apk files. Before the you need 7-zip software which is free.
Locate the folder C:\ProgramData\BlueStacks_nxt\Engine\ or bluestack engine folder which depends upon version of bluestacks
Locate your instance. For eg: my instance name is Nougat64 and it location will be C:\ProgramData\BlueStacks_nxt\Engine\Nougat64.
Here you will find a file name Data.vhd and you have to open it with 7zip.
In 7Zip go to app folder and here you will find all installed apps.
For eg: Here I want to locate instagram apk file then go to com.instagram.*
Developing an extension for Mozilla Firefox I wonder if there is an "easier way" to what I do right now. Currently I do:
Create a folder - in which to develop - for example myextension
Inside this folder: Create and Edit the Files (like install.rdf, chrome.manifest, xul files. Basically all the other structure of a Firefox extension (no problem here))
Zip-compress the content of the myextension to a ZIP-file (i.e. named myextension.zip)
Rename myextension.zip to myextension.xpi
Install the xpi-file-firefox-extension then in firefox
Restart Firefox
Test the extention
After each edit to the codebase of the extension I need to undergo the process of 3. zip-compress, 4. Rename, 5. install XPI file to firefox, 6 restart browser.
Of course I could automate some of this but still I wonder if there is another way to develop the firefox extension directly in the running firefox profile folder .
The extensions I know are stored in the Firefox profile folder as:
firefox/profile/extensions/nameofextension.xpi
I cannot remember well, but I think that there was a way to have the extension being stored unzipped as a folder there too? This way I would still need to restart after edits but not do all the laboursome zipping-renaming-installing.
Any ideas?
It is possible to setup a directory to "in-place-edit" a firefox extension. By this the effort between editing and testing of the Firefox-extension can be reduced.
I have found the good explanation on the blog https://blog.mozilla.org/addons/2009/01/28/how-to-develop-a-firefox-extension/
Here I want to give the principal steps necessary to achieve the "in-place-edit"
Step 1: You have to find your profile directory of Firefox.
For example in Linux this would often be often something like this:
~/.mozilla/firefox/#%#%.default/
Step 2: Go to this profile directory
Step 3: If you already have any extensions installed (like for example adblock+ or noscript), then inside this profile directory you will find a folder named extensions. If you do not have yet any additional extension installed, it might be easy to simply install any, only to have the **extensions" folder be setup for you.
Step 4: In this extensions folder you can create a new directory (let us name it "myextensions_1"), which shall contain the stuff of your plugin. This stuff would be the ordinary things like the install.rdf, chrome.manifest files and the content,skin,locale subdirectories. In effect all the stuff you would normaly zip up to become the XPI file.
Step 5. Create a file that is equal to the content of the <em:id> tag that you used in your ìnstall.rdf file. So if you used <em:id>myextensionname#author.org</em:id> you need to create a file named myextensionname#author.org. Inside this file you will write the location of the "in-place-edit-extension-folder" we created before. In our example this we would have
the file myextensionname#author.org
which contains only the text ~/.mozilla/firefox/#%#%.default/extensions/myextensions_1
Of course the text depends on the location of the folder you use for your plugin.
If you did all things correctly - and maybe double-checked with the instructions of the link above - you can restart or "newly start" firefox. The browser will ask you if you want to allow the usage of the plugin myextensionname#author.org, which you can conceed.
Now you can edit in the folder ~/.mozilla/firefox/#%#%.default/extensions/myextensions_1 and need not to worry about zipping-up -> renaming -> installing.
You simple restart Firefox and the edits to your extensions code will become available.
This will allow you swifter and faster developing "in-place".
Note: this is a shameless self-plug - I am talking about an extension I created myself.
Developing an extension in place is possible but has so many issues (mostly caching of all kinds) that it really isn't a good option. Still, you can simplify your development cycle a lot. For that you need to install the Extension Auto-Installer add-on in your Firefox. Then you can put a batch file (assuming that you are developing on Windows) into your extension directory along the lines of:
zip -r test.xpi * -xi *.bat *.xpi
wget --post-file=test.xpi http://localhost:8888/
del test.xpi
The required command line tools are all preinstalled on Unix-based systems, for Windows you can easily download them: zip, wget.
Then you will only need to run that batch file to update your extension in Firefox. If your extension isn't restartless then Firefox will restart automatically. So this replaces your steps 3 to 6.
I have a web folder on a Mac (running MAMP Pro) and have files been added within it on the fly, whose URL is as follows .
http://abc.com/folder/
I have another Windows machine that should constantly watch this folder and download any new file that gets dumped to this web folder to c:\macfolder\ (The files are always tsv's).
I know I can use wget to acquire files and run whatever program that would do this as a scheduler in windows to watch constantly, but whats the best way to watch this folder for the new files.
Thanks
P.S I do not know what are the best tags for this question. Help me out with that too.. :P
Since the directory already is mounted on Windows, your question appears to be a duplicate of this (and related) - assuming you're OK using C# to build such a tool:
Monitoring a directory for new file creation without FileSystemWatcher
If not so keen on the C# tool, there are command line solutions like this one here:
batch file to monitor additions to download folder
I have content to be installed, but it's file and folder layout is determined by the brittle, old, Windows installer. I can't fundamentally alter the structure, and I'd prefer not to alter it at all. I can't put it in a PackageMaker package and somehow get the Windows installer to figure out how to read it, for example.
Is there a way to use PackageMaker without having to bundle up the real content at build time? Is there a way to build the package with symlinks and have PM honor them at run time?
I need to support 10.5-6.
edit: If I could use an uncompressed package, that might be able to share the content files between installers. Is there way to do that?
I'll try to give more info about what I'm doing, if something isn't clear please let me know. Please forgive any redundancy.
I need to create a Mac/PC DVD to install my application. The application consists of either a Mac or Windows "reader app", and about a GB of "content" files. There is an existing Windows installer that reads installs the Windows reader and the content files off the DVD and installs them. It is (unfortunately) not a possibility to change the Windows installer. Therefore, the shared content files on the DVD must remain exactly as they are on the disk, I can not zip or package them up, or anything.
I need to make a Mac installer that will install the Mac app and the content. So, the installer needs to install the content from the folder structure of the DVD, which it will have to look at during install-time. My understanding is that PackageMaker requires you to package up the installed files during the creation "build phase" of the installer. That won't work for me because I can't alter the content on disk.
Sunil said:
During creating installer using packagemaker we can attach both a file and a folder also we can specify the path it will be installed. If u want customized way of storing the installed data eg- in some directory structure then in pre installed script write the script to create directory to be created.
I am not able to "attach" files or folder to the installer when I create it. I need the installer to read the content off the DVD when the user runs the installer.
Let me know if there is something that needs to be clarified further.
It sounds like you want the .pkg to copy the files right from the DVD, instead of having PackageMaker bundle the files into the .pkg, correct?
As far as I know a .pkg cannot do this natively. As NSD has mentioned you can do this in a postinstall/postflight script, but you want to display a proper progress bar. The only option left that I can see is to write a Cocoa app which not only copies the files off the DVD but also displays a progress bar in its GUI, and use that app as the postinstall "script".
During creating installer using packagemaker we can attach both a file and a folder also we can specify the path it will be installed. If u want customized way of storing the installed data eg- in some directory structure then in pre installed script write the script to create directory to be created. Can you please describe your problem more deeply so that i may help you
Write a postinstall or postflight script that copies the files off of the DVD.
How to run the exe file to other system?
Using VB 6
I copied the exe file to other system, then run that exe file, it not working it showing error
“component comdlg32.ocx or one its dependencies not correctly registered a file is missing or invalid”`
Can any one help me how to avoid this error?
When deploying VB6 applications, you should create a Setup, this will manage the DLL's that the VB6 application depends on. Since it is not enough to just copy the .Exe and .Dll's. You also need to register them.
The creation of the setup is included in the VB6 environment.
You can read this http://support.microsoft.com/kb/830761 which is very comprehensive.
1: http://support.microsoft.com/kb/830761 for more information.
Or if you just want the redistributable files check this kb http://support.microsoft.com/kb/290887
Copy and register the comdlg32.ocx on other system. Link: Fix Missing Comdlg32.ocx Run time Error in Portable apps.
Create an installer for your program.
Unless you are deploying your program to really old versions of Windows (prior to XP), one nice alternative is to create an XCopy package using reg-free COM. This is fairly easy for most simple programs using Make My Manifest though it can be done by hand or using other tools if you invest in a little study.
Even then a formal installer package is usually desireable though, if nothing else to create Start Menu shortcuts and set up application workspace directories.
Keep in mind that even the PDWizard is difficult to use blindly. Packaging and deployment is a topic that requires some learning investment.
Outdated or missing comdlg32.ocx runtime library is causing this error. Here is a copy of comdlg32.ocx (~60 Kb Zip). Download the file to the Desktop and extract the comdlg32.ocx to your the Windows\System32 folder.
Note: If you already have a copy of comdlg32.ocx, backup the existing file to a different folder and delete it from System32 folder.
1. Download comdlg32.zip and save to Desktop.
2. Unzip the file using WinZip or any other utility.
3. Extract comdlg32.ocx to Windows\System32 folder.
4. Type the following command from Start, Run dialog:
regsvr32 %Systemroot%\System32\comdlg32.ocx
Typically a VB 6 app will consist of an .exe some .dll libraries and a config.ini file. The exe is the starting place and it consumes the dll's and config.ini and other resources to run => you have to have all parts in the same directory for the app to run typically called "packaging" an app. E.g. An installer simply ensures that all those files in a packaged app are placed on a users computer in an Windows application directory, and creates a shortcut launch icon so that a user can click the shortcut in the start bar and the app will run.
To "package" your app (put the dll's and exe in the same folder) you can use an Add-In called "Package and Deployment Wizard":
And here is a demo of using it: https://www.youtube.com/watch?v=XT7jaoAiKDo
You can either package and create an installer and package or just create a package:
Now if the Deployment Wizard doesnt show as an add-in on your VB6 Editor Installation, go to editor's program folder and find the tools Tools folder, i.e:
Then you should be able to find the Deployment Wizard there:
Open it to use it.