I'm new to Trigger.io. I noticed there's no option to choose where Trigger Toolkit will be installed (Windows 7 32-bit). It always installs on C: drive (the System Drive).
My android SDK, AVD are on D: drive. When I go to local config, I can only browse within C: drive. I don't want to keep the Android folder, and even my app code, on System drive (It may have to be formatted without taking a back-up).
So my question is: Can trigger toolkit be installed anywhere, or do I have to copy my Android folder to C: drive? Also, can the Toolkit only browse in the drive it is installed in?
We have a story in our backlog to support switching between drives in the Toolkit - it's definitely on our radar.
In the meantime, can you can manually edit your local_config.json file (sitting alongside your src directory) to include the drive in the relevant paths?
Related
I need to recover the photos from a Windows 7 partition (Windows has been erased) external on a laptop running Ubuntu from a live USB stick. But I am not familiar with the Windows 7 file structure. I accidentally found a folder called Libraries containing all the photos. But now I don't seem to be able to find it again. I understand it is a virtual folder. How do I go about navigating to it again? I have tried systematically going through all the folders; I did find a folder called Libraries, but it is not the same as the one I found earlier on.
Thanks for any ideas.
Looking to create UWP APP using cordova.
The App needs to scan file system to get list of mp3 files on device, the device may be a desktop pc with windows 10 or a phone.
However the Cordova is able to see the virtual path and not C drive or D drive on device.
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onFileSystemSuccess, fail);
The winPath of the received FS object is something like below
C:/Users/{USERID}/AppData/Local/Packages/{AppNameSpace}_bzbj8h50hftv4/LocalState/
And this is root of the FS, can not move directory to C: drive, it is not allowing.
So Question is, does UWP or any windows platform does not expose Storage devices to Cordova apps? Or I am doing something wrong, as I am new to Cordova development.
For full file access in a UWP app, you will want to add WinJS framework to your app.
The plugins are going to be targeted to cross-platform support, and mobile devices have more restricted file access. Running on full Windows, you will have more capabilities available, but likely not supported by plugins.
Look at http://www.buildwinjs.com/ for WinJS.
I have an macbook air 2012, I recently installed Windows 10 in it using bootcamp.
I also downloaded the bootcamp drivers, and a folder named "BootCamp" and "$WinPEDriver$" were created in my Windows10 bootable usb. I was able to use it to install Windows10 and use it.
Then due to space issues I deleted the Windows partition, thinking I can always reinstall it, if needed.
Now I wish to reinstall it, but when I took a backup of the bootcamp drivers, I only backed up the "BootCamp" folder, I forgot to backup the "$WinPEDriver$" folder. Without "$WinPEDriver$" folder, Windows10 get installed without the drivers. When I try to manually start the setup.exe in BootCamp folder, it quits saying "$WinPEDriver$" folder is missing. So I created a empty folder named "$WinPEDriver$". With this the driver installation does proceed, but everything except the Broadcom_Bluetooth_Driver are getting installed. I tried to install the Bluetooth driver alone manually, that also didn't help.
So my question is,
Is there a way were I can download the "$WinPEDriver$" folder alone from Apple site. I live in a place where bandwidth is very low, so downloading another 2 GB of drivers will take 3 more days, and may also get interrupted frequently.
Or can I create the "$WinPEDriver$" folder manually, just as BootCamp Assitant creates it.
Or Is there a way to download the bluetooth drivers alone from apple site.
My bluetooth chipset information is Broadcom USB 20702A3.
Thanks.
Just create a blank folder called '$WinPEDriver$'and it'll work, I know you've probably sorted it by now but i thought i'd leave this here in case anyone else runs into the same problem.
I was able to download Apple bluetooth for windows drivers from a Parallels KB article on titled Unable to use Apple Bluetooth USB Host Controller in Virtual Machine
As for the "$WinPEDriver$" it is included in the newest version of Boot Camp Support Software 5.1.5769 although it is still large at 542.3 MB it is not the 2 GB you feared it would be.
The download includes both the BootCamp and $WinPEDriver$ folders.
Good luck!
Incase anybody needs this when you open up Bootcamp Assistant below the 'Action' tab there is a download button to install 'Windows Support Software'. You can download from there and plug in to the Windows by using flash drive or hard disk and make the setup.
I am running Windows 7 64-bit Ultimate under VirtualBox (latest version, 4.1.4) on my MacBook Air. I have created a shared folder on the Mac under my user folder. I have granted read/write privileges to this folder to my account. (I also configured it with read/write access to everyone, and that did not make a difference.)
In Windows 7 under VirtualBox, I have added that folder as a shared folder.
From within my Windows 7 VM, I can see this folder, create new folders and files in it, and read folders and files, using Windows Explorer.
The problem is with Delphi XE2. If I attempt to open or save a project to this shared folder, from the Save dialog box the share (which I have currently mapped to a network drive) appears with an red X icon indicating that there is something wrong with it. If I click on this folder, Delphi displays a dialog box with the title "Restoring Network Connection" and a message "An error occurred while reconnecting E: to \VBOXSVR\Demos VirtualBox Shared Folders: The request is not supported. This connection has not been restored."
That I cannot save projects in that shared folder inhibits my ability to easily create iOS apps and generate the necessary Xcode folders using Delphi's dpr2xcode.exe utility. What I have to do instead is to create the project folder locally, run dpr2code.exe to generate the Xcode project, and then to use Windows Explorer to copy the contents of the local folder to the shared folder, where I can then load the generated project in Xcode, compile, and run it.
Does anyone know of any configuration or steps I can take to permit Delphi to see the shared folder as a valid folder?
For the record, and I have seen a similar problem with other versions of Delphi with respect to Folders from a Delphi installation in VMWare Workstation (8.0) running under a Windows 7 host. In those cases, Delphi simply does not display the shared folder.
Switch your VM to "Bridged" networking as opposed to NAT.
In VBox, select your VM, go to Settings > Network > Adapter 1 > change "Attached to" to "Bridged Adapter"
I'm guessing you've already enabled SAMBA sharing on the OSX host (System Preferences > Sharing > File Sharing (switch it on) > Options > tick "Share files and folders using SMB (Windows)")
The reason you want Bridged networking is so that your VM is assigned its own IP address, rather than sharing the IP of your OSX host (which is what NAT does).
Give it a shot, let me know if it helps :)
EDIT: As it turns out, the issues described here were caused by an outdated version of the Adobe Air runtime. The Air app I had written was compiled for Air 2, but the computers were running Air 1.5. Updating the computers to Air 2.7 (the current version at the time of writing) fixed the problem. Unfortunately, running a newer Air app in an older runtime generates a misleading error. Beware!
ORIGINAL POST:
I'm building an Air app for internal use at my company. I need to install the app to a USB data stick, so that the installed app may be quickly moved from one computer to another. This works just fine on Macs, with the .air generated .app program running just fine on whatever Mac it is moved to.
When I do this on Windows, however, it only works on the computer that performed the initial installation of the .air file. Moving the stick to a different computer and running the program .exe results in an error message: "The installation of this application is damaged. Try reinstalling or contacting the publisher for assistance".
Is this the expected behaviour? Is there any way to run an AIR .exe on a USB data stick regardless of the computer that generated the EXE?
Just to be clear: I'm not looking to move the installer between computers, but the .exe that results from running the installer. I want to run the .air installer once, take the .exe result, put it on a data stick, and then run that .exe on any computer.
Simple recipe to make a portable Adobe AIR app
Ingredients:
A whole ziplock of Adobe AIR SDK, recently harvested from Adobe's server farm.
One .air package, fresh.
Command-line to taste.
Steps:
Extract the .air package with a 7-Zip blender.
In this folder bowl, whisk in the bin/adl.exe and runtimes/air/win from the SDK.
Take the META-INF/AIR/application.xml yolk and set aside.
Make sure to have adl.exe, win/ and application.xml in the folder casserole.
Add a pinch of adl -runtime win application.xml and let it simmer.
Optional: if you want shortcut sauce, just take note of the folder's location in your filesystem kitchen and re-write the parameters above so they have full paths to the win runtime and application.xml.
Finally, most .air will come with a baker's dozen .pngs in the icons directory. You can use an icon oven to grill these into a golden crispy icon.ico to be used in the shortcut sauce.
Bon appétit.
Compile the app to a native exe: http://www.beautifycode.com/compile-air-to-native-dmg-or-exe-files-with-ant. That should do the trick!
and http://help.adobe.com/en_US/air/build/WS789ea67d3e73a8b22388411123785d839c-8000.html
Update: for full stand alone operation look into shu-player, or http://dmartin.org/weblog/how-run-adobe-air-apps-windows-without-admin-rights
There's an easy method I always use (and I have never met the cases it hadn't worked).
Compile ".air" package, install it on your computer. After that, copy the following files from the app folder (keeping the directory structure intact) and run on any Windows machine which has the AIR framework installed.
Minimum set of files to copy:
\META-INF\AIR\application.xml
YourApp.exe
YourApp.swf
Once again, the limitation - your app can only be run on Windows.
In AIR 3 (in Beta right now), you can package an app as a "captive runtime bundle." On Windows this produces a folder that includes your app and the runtime itself. You can run the app from this folder without installation. Of course, some features won't work without installation. For example, registering file types for your app requires registry entries on Windows, so you would need an installer for that (or a utility program that set the required registry values would work, too)