日曜日, 2月 27, 2011

route-me: Creating a new MapSource Class

route-me: Creating a new MapSource Class

touchMapLite

touchMapLite

light javascript viewer for slippy map tiles, optimized for mobile devices. based on panoJS. developed for - openstreetmap data - (multi-) touch sensitive devices - webkit browser.


touchMapLite framework notes

水曜日, 2月 23, 2011

route-me Embedding Guide


■ ○route-me○
https://github.com/route-me/route-me
route-me is using GitHub to share code with you!



Old Stuff:
http://code.google.com/p/route-me/downloads/list
route-me
Open source iPhone-native slippy map.




■Git through a proxy(http://www.rootninja.com/git-through-a-proxy/)
git config -–global http.proxy http://172.20.203.128:808
簡単なやり方:
export https_proxy=http://172.20.203.128:808


■GIT clone over HTTP(http://rip747.wordpress.com/2008/09/12/git-clone-over-http-who-knew/)
git clone https://github.com/route-me/route-me.git


■EmbeddingGuide
▲How-to guide on making an application containing a map
http://code.google.com/p/route-me/wiki/EmbeddingGuide

△route-me Embedding Guide - GitHub
https://github.com/route-me/route-me/wiki/Embedding-Guide
▲Integrating with your own project
http://www.gisnotes.com/wordpress/2009/12/iphone-dev-note-19-route-me-opensource-mapping-for-the-iphone/

“Unknown class in Interface Builder file” error at runtime

“Unknown class in Interface Builder file” error at runtime

  1. Just call a method it inherits from NSObject, like +class.
  2. Set the -ObjC linker flag. In Xcode go to Project -> Edit Project Settings, find the "Other Linker Flags" entry and add the following (capitalization important) "-ObjC" without the quotes.
    Related linker option:
    -all_load: This one seems a bit overkill, as all of my unused classes will be kept in the final binary, potentially bloating it.
    -ObjC : This seems to be a compiler flag, and overrides the file extension rules.
    -lobjc : Need this special case of the -l option in order to link an Objective-C or Objective-C++ program.
  3. Fixed this by copying the text from my class.h and .m, deleting those class files from the project, and creating new class.h and .m files with the same name using "Add File".Then paste the code back into the new files, and everything work great.

月曜日, 2月 21, 2011

Put Mac OS dmg image to USB

Mac : Bootable USB from dmg image


sudo asr --restore --source /Volumes/MountedDMG-Disk --target /Volumes/USB-Stick --erase

金曜日, 2月 18, 2011

Corkscrew is a tool for tunneling SSH through HTTP proxies

Corkscrew
Corkscrew is a tool for tunneling SSH through HTTP proxies.

火曜日, 2月 15, 2011

Mount hidden partition from command line

Mount hidden partition from command line

  • Check bootsector to determine actual filesystrem with a hex/disk editor, like, as an example, TinyHexer
  • Use MBRfix to SET partition type to either 0B or 0C (if FAT32) or 07 (if NTFS)
  • Backup the MBR with dsfo/dsfi or dd-for-windows, or any similar utility
  • mbrwrwin.exe can mount the partition PQSERVICE easily
  • mount the partition PQSERVICE easily
  • If your PC use Vista or Seven, mount partition easily using diskpart command line.

    diskpart
    rescan
    list disk
    select disk 0
    detail disk
    list partition
    select partition 1
    detail partition
    set id=07 override
    list disk
    select disk 0
    list volume
    select volume 0
    assign letter=d

    for exemple...
    setid parameter (diskpart) is not available in xp
  • Typical examples of "mounting" apps are VDK, or IMDISK or Firadisk or WinVblock, i.e. disk/partition drivers. Or does it behave similar to the MOUNTVOL command or the good ol' mnt/unmnt by Christoph H. Hochstaetter or software like the one by Uwe Sieber:

日曜日, 2月 13, 2011

Beginner's Guide to Creating a VistaPE CD

Beginner's Guide to Creating a VistaPE CD

Creating a Windows PE Boot disk
Windows Automated Install Toolkit (WAIK)
TechNet Library -> Windows -> Windows Vista -> Windows Vista Technical Library Roadmap -> Deployment -> Windows Automated Installation Kit (Windows AIK) -> Phase 4: Image Deployment -> Deployment How-To Topics -> Work with Windows PE -> Windows PE Walkthroughs


WinPE-SRT-Package


Don't panic! This doesn't mean that it was removed from the Windows Vista DVD, but it does mean that our corporate customer's will now need to use the boot.wim from the Vista installation media to install WinRE on the harddisk or on WDS.

The OPK has not changed and WinRE is still part of that WinPE. If your customer has access to the OPK, they can use that in the meantime.

If a customer attemps to mount the WinPE.wim file from the Windows AIK and install the SRT optional component (which is WinRE) using PEIMG, SRT will not be listed as an option. Unfortunately, the “BuildWinRE.cmd” file is still included in the C:\Program Files\Windows AIK\Recovery folder. If a customer runs this batch file, it will fail because the component isn't there.

As a workaround, corporate customer's or those of us with access only to the Windows AIK can use the boot.wim from the Vista installation media to install WinRE to the harddisk or on WDS. Instructions are expected to come out soon, but until then, for those of you that want to get a head start or for those of you who receive calls on this, the instructions are posted below.

Note: I only posted Part 1 as the only thing that has changed is how you create the WinRE image. For the remaining steps, please refer to the topic titled “Walkthrough: Build a Windows Recovery Solution” in the Windows PE CHM file included in the Windows AIK. Just ignore Part 1 and replace it with the following:


Part 1: Creating a Windows RE Image
In this section, you will create a customized Windows RE Image on your technician computer.

Step 1: Copy Windows PE from the Installation Media
In this step, you will create a directory structure and set up a Windows PE image for editing.

1. On your technician computer, click Start, point to All Programs, then Windows AIK or Windows OPK, and then click Windows PE Tools Command Prompt.

The menu shortcut opens a command prompt window and automatically sets environment variables to point to all the necessary tools.

2. Create a directory for the Windows PE image and a mount point
mkdir c:\winre_image
mkdir c:\winre_mount

3. Copy the Windows PE image from the installation media using ImageX
imagex.exe /export /boot e:\sources\boot.wim 2 c:\winre_image\winre.wim “Windows Recovery Environment”

4. Mount the image using ImageX
imagex /mountrw c:\winre_image\winre.wim 1 c:\winre_mount

Step 2: Add custom Windows RE scripts
In this step, you will add a custom Window RE scripts to your image. You will create a script called winpeshl.ini that will launch the Windows RE shell at startup.

1. Using a text editor, create a file called winpeshl.ini that contains the following text:.

[LaunchApp]
AppPath=x:\sources\recovery\recenv.exe

2. Copy this file to \Windows\System32 directory in your working Windows PE directory. For example,
copy winpeshl.ini c:\winre_mount\Windows\System32

Step 3: Add mass-storage drivers (optional)
If necessary, you can include third-party drivers (.inf) in your Windows RE image by using the peimg.exe /inf command. For example,

peimg.exe /inf= c:\winre_mount\Windows
Where is the location of the. inf file.

Step 4: Add custom tools to Windows RE (optional)
You can customize Windows RE shell by creating an .xml file called WinREConfig.xml. WinREConfig.xml enables you to define custom support and diagnostic tools within Windows RE. This step is optional. For more information, refer to the Appendix.

Step 5: Save changes to the image
In this step, you will save all the customizations into the image file.

1. In a Windows PE Tools Command Prompt window, unmount the image by using ImageX. For example,
imagex.exe /unmount /commit c:\winre_mount

2. Copy the Windows RE image and related files onto a UFD device

copy c:\winre_image\winre.wim f:
copy “c:\Program Files\Windows AIK\Tools\PETools\x86\boot\boot.sdi” f:
copy “c:\ Program Files\Windows AIK\Recovery\setautofailover.cmd” f:
This completes Part 1 of installing Windows RE. To install the Windows RE image onto the hard disk, follow the instructions in Part 2a or Part 2b. To create recovery media, for example, a CD-ROM, you can create an .iso file of your custom image and burn it to a CD-ROM. Follow the instructions in Part 3.