got off to a late start publishing this year, since the survey appears off a degree or two from 'true' north. it happens. so i've been adjusting and confirming points as i drive around.
this is a garmin formatted street vector map, you can use with most garmin gps models. upload the map using the sendmap.exe program, or copy the file to your memory card if you have a newer model with a memory card
black rock city 2010 img file
sendmap20.zip (contains to sendmap20.exe).
turns out, you can add entries that will cause the iphone auto-correct to skip words you don't want the phone to prompt or modify.
the iPhone auto correct feature is great but sometimes it changes words you simply don't want to be changed. I use with Inspell with "duplicate" entries for words i want the iphone auto correct to leave alone. example, the phone keeps prompting to turn 'yo' into "to", which just doesn't work well for me. so i put an inspell entry that specifies 'yo', with 'yo' for the replacement entry (e.g. no change).
'yo' -> 'yo'
so now the phone does not prompt to auto-correct the word 'yo'. i'm guessing this must work by automatically replacing with the 'original' with the correction as you type, which matches the current selection (the original word) therefore avoids the prompt (or at a minimum, the *appearance* of invoking the prompt)??
you can shell to the command prompt and try to fix it.
- su root
- apt-get update
[If you see errors, it's probably in /var/lib/apt/lists]
i ran the apt-update command a couple of times, then went to Cydia and reloaded any out-of-date apps. appeared to me this command alone cleared out the stuck downloads. the original recipe continued:
- apt-cache policy cydia
[If you see errors, it's probably same as above]
- cd /var/lib/apt/lists
- rm *
[If something is in "partial" directory, go there and rm * that too. When done, do: apt-get update]
- cd /var/lib/apt/lists/partial
- rm *
- apt-get update
also here are some important commands:
apt-get update
apt-get upgrade
apt-get autoremove (removes packages that you dont use anymore)
I don't know if the default is open access or my settings got switched, but the iphone mail app (Mobile Mail) downloaded an image.... whatwhat? grrrr.
To make sure iPhone Mail does not download remote images in emails (which would reveal your opening the message to spammers and your approximate location, too):
Go to the Home screen.
Open Settings.
Tap Mail, Contacts, Calendars.
Make sure Load Remote Images is not enabled.
I'm also trying out the Cydia/RockYourPhone 'Firewall' app. I have a few UI complaints but in general it's working and should help prevent inadvertent access (outgoing traffic) by rogue mail like this, or other apps.
]]>Honorable mention:
Essentials:
I'm more utilitarian about my apps, all of these either correct an artifitial limit or significantly improves how my phone works -making the phone do more for me.
]]>To: +1-250-555-1212
Message: 111Hey Steve -- give me a call ASAP
The recipient of the message won't receive the "111" or "*noti#" at the beginning of the message, but you will receive a confirmation that it has been delivered to their handset. Note that not all GSM networks support this feature e.g., Fido in Canada supports 111, T-Mobile supports *noti#
i tried the *noti# on tmobile, and got a separate message back stating the message had been delivered. I'm not sure if this is just a GSM system feature, perhaps other providers offer something similar.
i wondered if i was out of the game, being on tmobile and potentially blocked by apple? what about others? i stumbled on some very promising posts. the basic issue is an updated jailbroken phone does not contain a certificate key-pair to uniquely identify the phone, which is required over the data network (rather than the cell network). using a key-pair certificate is a good approach to solve the problem. the phone pings the server letting it know what IP to use, etc. itunes happens to add this certificate when a phone identified, apparently just before actual 'activation'.
the unique requirement wasn't clear at first, and there are solutions that have you download and install a certificate, either using software to manage the process or manually with root terminal access. people posted using this solution, and got push notification working on various networks. very promising!
for obvious reasons, a lot of the folks who used this solutions posted that they got notifications to work and indeed were getting push notification. just not theirs. instead, they were getting notifications intended for other people. basically everyone else who was using the same certificate and application, anywhere on the planet.
likewise for me, at first it seemed like it worked. rather, i was getting notifications in various languages with strange names attached. none of them for me. it was entertaining. and while entertaining, it was just not useful.
fail!
my first attempt with the common certificate file, i just used a cydia package to load the cert files. for good measure i went through the manual process, having already downloaded the files. no surprise, i got the same result and it's pretty clear why using a common cert file. the cydia packages was later removed since this solution just does not work, and anyone who reported it did work (getting their messages) was successful for other reasons, if at all.
you must have a unique certificate.
it's also possible to get a certificate if you use an ATT sim when you load the firmware, then wait for itunes to generate the certificate just before you activate the phone (use slide to cancel). you have to wait for some time for itunes to acknowledge the phone and pass emergency-only mode (some reporting it never registered, i don't know i've never done it in this manner). also it's not clear, if you do this and then restore a backup on the phone --you may overwrite that new certificate file defeating the purpose. or not. i didnt try this. having already passed this step.
however, i do have an att sim and just for grins i swapped cards and tinkered about to see if i could invoke a similar result without reloading the firmware. i didnt try really that hard. anyway, no dice.
doing a little more (all night) searching around i stumbled on pushfix.info and software to load a new generated 1024 bit certificate key-pair on the phone. faced with the other option wiping the phone, starting from scratch without backup and having to build up software and settings --this was a much more appealing option. the solution sells for $6, and worth it to me if it solves the problem while keeping my current install in place. yah, totally worth it.
pushfix 2.0 also comes along with a nice simple app to test the phone so you know if it's working or not pretty quickly.
the pushfix.info solution:
for good measure, uninstall and reinstall any apps using push notification. follow posts/guides on pushfix.info, if that alone does not appear to correct push notes for a specific app. that pretty much knocked this one out of the park. i have my push notifications working on my phone without reloading firmware from scratch.
huzzah!
here's the alternate solution posted by someone else. these are steps i did *not* do, but you can try and may work. jury is out over restoring a backup afterwards? if anyone knows you can post here?
1) I placed the AT&T sim in the iPhone
2) Restored to 3.0 firmware
3) it allowed me to enter the springboard and said awaiting activation so I dismissed it
4) optional? went into settings and turned OFF the 3G signal.
5) Ran Redsn0w
6) went into cydia and ran Ultrasn0w
7) turned off iPhone
8) Swapped out AT&T sim with my T-Mobile sim
9) turned on iPhone
so i have a jailbroken & unlocked iphone on OS 2.2.1. since i previously used quickpwn before to jailbreak my phone, i was waiting for a familiar updated version for the new firmware to upgrade the phone to the newer OS 3.x firmware. too many month have passed, and i started to give up waiting for a quickpwn release, so i began to wade through various beta releases of redsnow and blackrain. i almost just went ahead with the mac version that was released, but continued to hold out for a windows version. i was in no rush, had a working phone and could wait for a while.
however, more and more apps were requiring the new firmware, forcing an upgrade to OS3.x (even though some of those apps did not leverage new features, but whatever i wanted to upgrade eventually). the time came, so i poked around more and found a recent redsnow release with updated firmware to v3.1.2 along with fairly thorough step-by-step instructions. good! I decided to run with this.
ok. the first step. *backup items on the phone*, did a full synch in iTunes... then added remaining contacts, more cleanup, swap contacts between outlook and the phone, some more clean-up. okay, one more backup and full synch in iTunes again. just getting the phone prepped, get my data squared away --all this just to make sure after i upgrade the firmware (which will wipe data from the phone), iTunes it will be in a good position to restore the data back on the phone. done and done.
reading some instructions. i took the suggestion that you should update to the latest iTunes version, most people confirming that v9.0.3 will not impeded the unlock/jailbreak process. ok, time to update. so i installed iTunes v9.0.3, and sync the phone *again*
this part alone took an hour or so. but now i'm ready. now some prep work for the upgrade:
i've download files firmware IPSW file (iPhone1,1_3.1.2_7D11_Restore.ipsw), bin files, and redsnow v0.9.2 for windows. interesting note: on reading more about redsnow, turns out this is actually the engine behind the quickpwn software i was using previously? curious.
alright, appears everything is set. it's go time.
[note: i should have tested an initial run of redsnow to make sure it will not crash? it loads and evaluates the firmware file first and may fail then, which will set you back. you can test this part without the phone.]
first step to update the firmware is to "restore" the phone using the downloaded firmware file using iTunes (shift-click restore, manually select the file). done. takes a while, but this part is fairly straight forward.
now for the magic! launch redsnow, load the same firmware file just restored to the phone in redsnow. it begins to load the file and --and reports ramdisk crash?!
Dead stop. fail. Blargh.
Okay. gotta do some research. online comments suggest you should run redsnow as administrator. i'm on an older flavor of windows xp, already running with admin permissions, so this comment doesn't really apply but i try it anyway. this is really more for 'Vista' versions or whatnot. it's a valid recommendation there but not really applicable for me. another comment suggested rebooting. queue line from 'the IT show', "have you tried..."
still not working.
damn wish i had done that initial test of redsnow i mentioned first, could have had that squared away prior to fussing with the phone. now my phone isn't working (well locked now, only allowing emergency calls). but we're here now, so let's deal with it. on a whim and without much else to fuss with, I try another machine laying around to see if redsnow will work there. i use my 'spare' laptop. pretty much same vendor, similar model. but here's hoping. redsnow launches properly without crashing. excellent.
i'm still not sure why it failed to run on the first laptop, but it works over here, so i just move forward with that. with redsnow running, time to plug in the phone, the system immediately finds the new usb device named USB DFU device (generic name?) prompts for a usb driver. okay. right, sure?
i'm not really sure what to do, 'i confirm to search online this time only', expecting it should just load a generic driver of some kind, similar to the common mass storage drivers. disregarding the issue more or less, i let redsnow continue to run, figure it will be fine anyway. redsnow continues, the next screen prompting me to put the phone into dfu mode. i put phone into DFU mode (actually pretty good at this), and screen goes black (totally normal, for DFU mode).
However, redsnow does not detect phone. try again. repeat, try again. this is taking over a minutes on each attempt. ok. not working, it's not fine. so i reboot the laptop to try that. i reboot other laptop, in order to try redsnow again over there. not working. try again. screen is still black. getting worried, as nothing is working.
Basically, nothing works and the screen is still black. i begin to doubt the phone is powered on at this point. i *thought* it was in DFU mode, but it doesn't really appear to respond to any keys. the usual hold the power-key to prompt for shutdown no longer works, and it won't turn on either. i start to think it's actually *not* on, and begin to think my phone is 'bricked'. grrr.
insert minor freak out.
however, i realize here that phone actually is in DFU mode (there is an audible add/detach prompt by the system, which tells me the phone is alive and kicking, interacting with the laptop in some way). then i remember to use home+power key combo (hit home first, add power key and hold both to force shutdown, until the unit powers off). simply holding power button does not work in DFU mode (because there's no screen interface to interact with the user?
ok. so i can power-cycle the phone. this means i can start all over or try again, hopefully getting things right, this time. let's start with redsnow, and try again.
now redsnow crashes on spare laptop?? just great.
i have no idea why this laptop won't work now, but i consider that the recent reboot may have started/stopped various services that were previously running, causing compatibility issues. so i start staring at services, having little idea where to start. then i notice 'removable storage' service is not running, and that sounds familiar to 'ramdisk'. it works now!
i'm back up and running with redsnow and it passes the ramdisk part, so we're back in the game. note: this was running on the first laptop, so there is some other conflict there). but redsnow STILL does NOT detect DFU mode, regardless of putting phone in DFU mode, which i can do blindfolded now. also notable, the system does not prompt for USB driver again when i plug the phone in, which seems odd. hint: attaching usb device that does not start has a different audible double-beep tone alert prompt than the normal attached device sound. so i try another usb port since most devices register the new address as a difference device and prompt for the driver again, maybe that will help?
taking a look at the system devices, i notice the 'USB DFU device' appears in system with '?' icon (not starting). i figure i need a driver and start looking for one, but quickly realize this comes from iTunes. However, I had not installed iTunes on this laptop. okay, there's hope.
so i install 9.0.3 on spare laptop, which should installed the required files. iTunes notices the iPhone so all good here. i plug in the device, however the device driver still reports an error, and no dice with redsnow. i then manually uninstall the 'USB DFU device', plug the phone back in, and the system notices device and installs proper driver this time. now, quit iTunes and try redsnow again, without apple service running (trying to prevent a conflict with iTunes). this does not work.
wtf. okay runnning out of things to try i *start* the apple service 'Apple Mobile Device'. this is the part where i just keep trying things until beating them to death, trying all possible variations until it's clear what will result. now I have redsnow running as well as 'Apple Mobile Device' service running (but not the iTunes app). progress! redsnow finds DFU mode and begins install. after several screens, says waiting for reboot. this is normal. we're on the way again!
It stays on this screen for a long time. a very long time. basically, i'm stuck on this screen. frequently patience here is better than ripping out items mid-process. and while i've been working on this all night and now all morning, i can be patient for this part to finish, just a little longer. any minute now. any. minute. maybe just wait some more. start researching while i wait. lots of other people with this issue.
most online comments suggest that you unplug/re-plug cable, that alone should do the trick. so i try this. does not work, try again with various delays plugging the cable back in. reboot phone manually, and try that, reboot into DFU mode, no dice. grrr. ok (i'm a bit concern that redsnow will just crash when i restart it, but i'm out of things to try). so i hit cancel (redsnow exits instead of back one step?), and i restart redsnow. it launches fine (whew), and i'm back into updating the phone. this is somewhat routine with these updates, most other times i've have to update the phone it did not work top-to-bottom in a single shot.
and this time it gets past screen. zomg.
**success**
i synch the phone back to original laptop to put data/photos/apps back on phone. most of the standard apps come back with the backup. awesome. all in all, the update should have taken a hour or so, with ten minutes of magic unlocking the phone, plus time to restore data and apps back on the phone. instead i lost 4+ hours unlocking the phone alone. the whole process was roughly 7-10 hours start to finish. another day fine tuning settings and favorites.
at some point i notice my contacts were shuffled around between two different groups/folders (one for outlook and one for the iphone). this is about the oddest thing i've seen as a result from this process, requiring a bit management to sort them out. in theory i have the phone just synch to the outlook and everything works dandy. but the update appears to have mixed some up. at least, this is how it looks. something may have happened in the first step with the update to the latest iTunes, I'm not sure. I should have backed up outlook alone etc etc. but in this case i skipped that step. damn.
fortunately outlook automatically marks 'created date', and 'modified date' on all items, and makes these attributes readily available to sort by. this is awesome, and makes management a breeze when it comes time to handling updates or figuring out what's going on when things like this happen. all the inadvertently shuffled records stuck out with a modified datetime, and were easy to find.
takes me about another day to resynch various cydia apps, modded features and settings. all good now. another to download new apps, new mods and get things squared away.
i've downloaded the 'backgrounder' app to background my APRS app, so now I can update positions in the background while using the phone or another app. rock on. next, i need to download a suitable wifi-tethering program (again). [word is the 2G phone does not include hardware for bluetooth tethering, or stereo audio,etc. i'm not sure if replacing the bluetooth stack in software will solve that problem or not].
summary, it's difficult to brick the 2G phone, the firmware updates appears based on hardware and you can manage that regardless of what state you put the phone in (hard reset)? --and you should plan on this process taking anywhere from ten minutes to ten hours. damn!
all good now.
be sure to read the update over push notifications yar!
this code snippet is for 'comma' delimited output.
SELECT
CASE PATINDEX('%[,"\r\n]%', [MyColumnData])
WHEN 0 THEN [MyColumnData] -- not found
WHEN NULL THEN [MyColumnData] -- unknown
ELSE '"' + REPLACE([MyColumnData],'"','""') + '"' -- encode data
END
AS [MyEncodedOutput]
there is a setting on the unit to auto detect this mode (media player if capable?). however you can force the unit into storage mode and navigate the drive.
Go to Settings -> USB -> Choose MSC
]]> When you connect it to your computer it will show as a drive. Open the drive you should see the folders.------------------------------------------
* If you do not see "Music" folder you should do the following.
On your computer Start -> Settings -> Control Panel. When you go to control panel window on the top Tools -> Folder Options -> View. In the selection make sure "Show hidden files and folders" selected.
------------------------------------------
random review:
The good: The Sansa View digital media player is an incredible value considering its features, which include photo and video support, a microSD card slot, an FM radio, and a voice recorder. The screen is relatively large, and there's a separate podcast menu for easy sorting of such content. It works with Mac and Windows and supports WMA subscription services and Audible.
The bad: The Sansa View is large for a flash player, and the onscreen interface is somewhat uninspiring. The small center select button may present a problem for some users.
The bottom line: If you value features and price over a flashy interface and excellent sound quality, the SanDisk Sansa View digital media player is definitely worth a look. It's easy to use and offers a relatively large screen and a memory expansion option.
------------------------------------------
some quick specs:
dimaneions: 4.3 inches by 1.9 inches by 0.4 inch
diagonal screen size 2.4
screen resolution 240 x 320
internal flash memory 8Gb
microSDHC slot (external, 16Gb limit? ~= 24gb unit max?)
internal lithium polymer (5 hours video, 32 hours audio)
voice recording, built-in microphone
built-in FM radio
USB 2.0 via cable
In addition to standard MP3 files, the Sansa View can play back a healthy array of other digital media files. There's direct support for JPEG photos and MPEG4, WMV, and H.264 videos. This player can even take videos purchased from services such as Amazon Unboxed and TiVoToGo, and it should have no problem with video podcasts acquired through iTunes. The Sansa Media Converter, available as a download, can transcode other (unprotected) formats for View. On the audio side, you get support for WAV, AAC (unprotected), Audible, and both protected and unprotected WMA. The player will work with any Windows Media-based audio service, such as Napster or Rhapsody. If you get tired of digital audio, switch over to the onboard FM tuner, which features autoscan and 20 preset slots.
output was 13.6 grams of diesel. average density of diesel listed at 0.85 kg/l, so that's 16 milliliters of fuel.
the espar manual states the fuel delivered in this startup cycle should be between 3.4ml and 4.65ml. so, much less. it was also clear after operating for a few minutes, that excess fuel was not being burned off and the unit was spewing smoke like mad.
so the pump output is too strong, waaay too much fuel. so i'm still looking for a proper esbar fuel pump (mfg. part: 25 1830 45 00 00), any tips?
on a curious note, the heater contains fairly advanced microprocessor, electronics, and sensors. they are reasonably well built and remarkably intelligent. i had not realized the level of sophistication these 'simple' heaters enjoy, it's pretty amazing. now, only if it worked. sigh.
]]>there are a number of well known, publish standards and specs.
this is the format i got scanning one of my cards:
;4111111111111111=1201=LAST/FIRST
]]> More research yielded this info, and potential for encoding:Data is laid out on a standard magnetic card in three tracks. A magnetic stripe card may have any of these tracks, or a combination of these tracks.
Track 1 was the first track standardized. It was developed by the International Air Transportation Association (IATA) and is still reserved for their use. It is 210bpi with room for 79 7-bit characters.
Track 1 is encoded with a 7-bit scheme (6 data bits plus one parity bit) that's based on ASCII. If your reader does not perform the ASCII conversion, all you have to do is add 0x20 to each byte to turn it into ASCII (there are no "control" characters). The seventh bit is an odd parity bit at the end of each byte.
Track 2 was developed by the American Bankers Association (ABA) for on-line financial transactions. It is 75bpi with room for 40 5-bit numeric characters.
Track 2 is encoded with a 5-bit scheme (4 data bits plus one parity bit.) To convert this data into ASCII, add 0x30 to each byte.
Track 3 is also used for financial transactions. The difference is its read/write ability. It is 210bpi with room for 107 numeric digits. Track 3 is used to store the enciphered PIN, country code, currency units, amount authorized, subsidiary account information, and other account restrictions.
Track 3 has the same properties as track 1 (start and end sentinels and an LRC byte), except that there is no standard for the data content or format. Track 3 is not currently used by any national bank card issuer.
In those rare systems where the PIN is stored on the card, this is the track where it is stored.
Additional reading
Additional Reading on Magnetic Cards
For more information of this topic, read the ANSI/ISO 7811/1-5 standard. This document is available from the American Bankers Association.
Other standards documents covering related topics include:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
]]>Here's the message: Rule Reporting Services Catalog Temporary Database File Existence failed.
"The Reporting Services catalog temporary database file exists. Select a Reporting Services files-only mode installation."
e.g. see folder under C:\Program Files\Microsoft SQL Server
]]>