Monday, July 25, 2011
Commodore keychain
I was looking through my boxes of stuff, and I found this Commodore keychain. This keychain is in it's original plastic bag. It was given as a gift for Amiga 500 computer buyers, around year 1989.
Thursday, February 3, 2011
Visual Studio 2008 intellisense not working - solution
I have many times struggled with Visual Studio compile problems. Most difficult problems to solve are problems which seemingly don't have any reason! For example the intellisense is showing return type string, but you know the return value is int.
The reason is that intellisense is storing data from old headers, and for some reason is not clearing it's database, but keeps giving you (and compiler) wrong information.
The solution is simple, simply remove the file $solutionname.ncb from your solution folder.
Note: you need to close your solution first!
The reason is that intellisense is storing data from old headers, and for some reason is not clearing it's database, but keeps giving you (and compiler) wrong information.
The solution is simple, simply remove the file $solutionname.ncb from your solution folder.
Note: you need to close your solution first!
Apps in iTunes grayed out - solution
Recently I encountered this strange error with iTunes and my iPod touch: I downloaded some applications from appStore and went to iTunes->Devices->"myipod" and chose "Apps" from the top bar, the application editor that opened was grayed out.
I was able to sync photos and videos correctly, but unable to install or manage the applications.
Solution:
1. I disabled restrictions completely from my iPod
2. Closed iTunes
3. Reconnected the iPod to my laptop
Really, I had to remove everything from iPods restrictions, not just only "installs".
I was able to sync photos and videos correctly, but unable to install or manage the applications.
Solution:
1. I disabled restrictions completely from my iPod
2. Closed iTunes
3. Reconnected the iPod to my laptop
Really, I had to remove everything from iPods restrictions, not just only "installs".
Tunnisteet:
iTunes app sync grayed out
Wednesday, January 6, 2010
Solution for Invalid MS-DOS function while copying from SD card
Recently I got "Cannot copy file: Invalid MS-DOS function" when I was copying digital images from SD card to my laptop. The reading device was my laptop's internal card reader and the card was 4 GB Kingston SD card.
Nothing worked for this particular file: no copying, no renaming and no deleting. Every operation ended with this "Invalid MS-DOS function" error.
Then I thought, that back in the days disk drives were quite picky about reading and writing certain disks. Perhaps it is true also with modern memory cards, too. So I took my external card reader, put the SD card in that, and I was able to copy the file without problems.
So, one possible solution for "Invalid MS-DOS function" resulting when copying file from SD card, is simply to use another (different) card reader.
Nothing worked for this particular file: no copying, no renaming and no deleting. Every operation ended with this "Invalid MS-DOS function" error.
Then I thought, that back in the days disk drives were quite picky about reading and writing certain disks. Perhaps it is true also with modern memory cards, too. So I took my external card reader, put the SD card in that, and I was able to copy the file without problems.
So, one possible solution for "Invalid MS-DOS function" resulting when copying file from SD card, is simply to use another (different) card reader.
![]() |
| Check out Angry Birds soda cans |
Tunnisteet:
Invalid MS-DOS function,
Invalid SD card
Sunday, December 27, 2009
How to fix LG tumble dryer error "EHE" or "ELE"
My LG brand tumble drier, model TD-C70210E, suddenly gave me error "EHE" just seconds after start. And of course the warranty period was passed just with one week, how likely is that?!
After testing, and after some "EHE" errors I also began to got "ELE" error code. The manual and internet didn't give any DIY solution for these, just advice to call LG repair service engineer. I also tried the "leave the drier door open and leave it like that for about one hour" solution, but it didn't work.
But luckily I solved my "EHE" error with this amazingly simple trick, that I found out myself.
1. Start the drier normally
2. Before the "EHE" error appears, open the drier door!
3. Because the door was opened during program, "dE" error is shown
4. Close the door and press "start/pause" to continue
5. Program will continue normally; problem fixed!
Before calling repair service, you should first try and test this really simple trick. It may also work for you!
After testing, and after some "EHE" errors I also began to got "ELE" error code. The manual and internet didn't give any DIY solution for these, just advice to call LG repair service engineer. I also tried the "leave the drier door open and leave it like that for about one hour" solution, but it didn't work.
But luckily I solved my "EHE" error with this amazingly simple trick, that I found out myself.
1. Start the drier normally
2. Before the "EHE" error appears, open the drier door!
3. Because the door was opened during program, "dE" error is shown
4. Close the door and press "start/pause" to continue
5. Program will continue normally; problem fixed!
Before calling repair service, you should first try and test this really simple trick. It may also work for you!
![]() |
| Check out Angry Birds soda cans |
Tunnisteet:
EHE,
ELE,
error code,
LG,
tumble dryer
Friday, March 20, 2009
Installing signed Java midlet with Nokia Application Installer, midlet appears not to be signed
Problem
I had the following problem: my Java midlet was signed, but when using Nokia Application Installer (comes with Nokia PC Suite), it showed the midlet as coming from not trusted 3rd party.
The jad-file clearly showed me that it actually was signed, but the installer in the phone told me that it was not.
And as the midlet appeared not signed, it was constantly nagging about read/write/connection permissions. That was not acceptable.
Reason
I then sent the files, BOTH jad and jar, to the phone via bluetooth. When installing the midlet with jad sent over bluetooth, the installer recognized the certificates, and the application was installed nicely.
Then the reason to the problem hit me: the jad had different filename as the jar! The jad was named MyApplication.jad, and the midlet was named MySpecialApplication.jar.
It seems that the Nokia Application installer does not read jad-files, and then discover the mentioned jar-files, but actually it reads first the jar files, and then tries to find jads with the same filename.
Solution
A) Just rename the jad, to be able to install the midlet with Nokia Application Installer. Or even better, change your project settings in Eclipse (or in whatever IDE you are using), to produce correctly named files.
or
B) Stop using application installer, and start sending the jad and jar files to the phone via bluetooth yourself.
I had the following problem: my Java midlet was signed, but when using Nokia Application Installer (comes with Nokia PC Suite), it showed the midlet as coming from not trusted 3rd party.
The jad-file clearly showed me that it actually was signed, but the installer in the phone told me that it was not.
And as the midlet appeared not signed, it was constantly nagging about read/write/connection permissions. That was not acceptable.
Reason
I then sent the files, BOTH jad and jar, to the phone via bluetooth. When installing the midlet with jad sent over bluetooth, the installer recognized the certificates, and the application was installed nicely.
Then the reason to the problem hit me: the jad had different filename as the jar! The jad was named MyApplication.jad, and the midlet was named MySpecialApplication.jar.
It seems that the Nokia Application installer does not read jad-files, and then discover the mentioned jar-files, but actually it reads first the jar files, and then tries to find jads with the same filename.
Solution
A) Just rename the jad, to be able to install the midlet with Nokia Application Installer. Or even better, change your project settings in Eclipse (or in whatever IDE you are using), to produce correctly named files.
or
B) Stop using application installer, and start sending the jad and jar files to the phone via bluetooth yourself.
Tunnisteet:
midlet signing,
Nokia Application Installer
Monday, December 1, 2008
Subscribe to:
Posts (Atom)

