If you download a PayPal statement as a PDF or other form as a PDF, you may view it in Apple's Preview, but when you print it, it prints a blank page.
Here is a work around.
Right click on the pdf in the finder, choose 'open with' and choose Chrome.
Down in the right, choose print.
It comes up blank. Tick the box that says "Fit to page" and there it is. Print and it will print correctly.
For some reason fit to page in preview does not fix the problem.
It may work with other browsers, I chose Chrome.
As far as I know, it may be related to updating to El Capitan.
Over and Out!
Friday, October 16, 2015
Tuesday, August 25, 2015
Tmart.com and Their 90 Day Money Back Guarantee
Simply put, Tmart.com's 90 Money Back Guarantee is not to be believed.
I had an Escam 300 that stopped working after just two weeks.
After several emails insisting on my money back they issued an RMA.
Their policy is when you send the item, you are refunded. This is not true,
they have to receive it first, then you are PARTIALLY refunded. Not a full refund.
See pic of email.
Bottom line - terrible service, can't be believed.
Tuesday, June 30, 2015
Bar Code for LV Sun LV-10U 10 port charger.
Bar code assigned to LV Sun LV-10U 10 port universal USB charger.
Clean up your desk from those pesky single USB charger adaptors and
condense them all to on sleek 10 port charger.
10 ports at 1 Amp or
5 ports at 2.4 Amps
great for charging Ipads and other accessories.
Bar Code 820103966917
Can be bought here:
http://www.ebay.com/itm/60-Watts-10-Port-USB-Wall-Charger-Multi-Port-for-USB-Powered-Devices-Universal-/231142751926?
Clean up your desk from those pesky single USB charger adaptors and
condense them all to on sleek 10 port charger.
10 ports at 1 Amp or
5 ports at 2.4 Amps
great for charging Ipads and other accessories.
Bar Code 820103966917
Can be bought here:
http://www.ebay.com/itm/60-Watts-10-Port-USB-Wall-Charger-Multi-Port-for-USB-Powered-Devices-Universal-/231142751926?
Saturday, May 30, 2015
Fixing A Dead LiPo Battery
This involves a Zippy 3 cell 25C Series 200mAh battery and the Turnigy Compact Charger E3.
I was using my Zippy 3 Cell battery to power my string of LEDs that I use over my work bench.
I forgot to unplug it before going home. The next day I see the LEDs are very faint, but still on.
I disconnect my Zippy 3 Cell LiPo battery and check the voltage. It's 7.4 V. I think, oh well, I wasted this one. I put it in my Turnigy Compact Charger E3 2S/3S charger. I bought both from HobbyKing by the way.
The charger flashes the 3 red LEDs stating that the battery is dead and can't be recharged.
So I thought, well let's charge it up another way and see if it takes a charge.
First, I put the battery on an area that was immune to damage from fire in case the Zippy exploded or caught fire. I hooked it up to my el-cheapo HY1803D DC power supply by Mastech.
I fed about the same voltage of the battery (7.4V) into the large gauge wires (the load side, not the wires that hook up to the charger.) I slowly raised the voltage with the amperage potentiometer at minimum.
I could see amperage jumping around between 1 A and 0 A. I tried to maintain about 30 mA. It didn't take long before I slowly raised it up to about 9 V with minimal current. I then hooked it up to the Turnigy charger, and it started charging again.
Next day I came into the shop, and it was fully charged.
One LiPo saved.
Hopefully this article will save more LiPo's from going into the landfill.
I was using my Zippy 3 Cell battery to power my string of LEDs that I use over my work bench.
I forgot to unplug it before going home. The next day I see the LEDs are very faint, but still on.
I disconnect my Zippy 3 Cell LiPo battery and check the voltage. It's 7.4 V. I think, oh well, I wasted this one. I put it in my Turnigy Compact Charger E3 2S/3S charger. I bought both from HobbyKing by the way.
The charger flashes the 3 red LEDs stating that the battery is dead and can't be recharged.
So I thought, well let's charge it up another way and see if it takes a charge.
First, I put the battery on an area that was immune to damage from fire in case the Zippy exploded or caught fire. I hooked it up to my el-cheapo HY1803D DC power supply by Mastech.
I fed about the same voltage of the battery (7.4V) into the large gauge wires (the load side, not the wires that hook up to the charger.) I slowly raised the voltage with the amperage potentiometer at minimum.
I could see amperage jumping around between 1 A and 0 A. I tried to maintain about 30 mA. It didn't take long before I slowly raised it up to about 9 V with minimal current. I then hooked it up to the Turnigy charger, and it started charging again.
Next day I came into the shop, and it was fully charged.
One LiPo saved.
Hopefully this article will save more LiPo's from going into the landfill.
Thursday, September 11, 2014
Errata for: Sams Teach Yourself C Programming in One Hour a Day, Seventh Edition
I'm currently reading Sams Teach Yourself C Programming. Although not new to C, I like to relearn and read works on C programming. In this post I thought it would be good to keep my own errata page on this book as it seems the website for tracking errata from the publisher is not yet updated.
Check back often as I go through the book I will update the errata here. If you have any errata yourself, please let me know and I will add it.
Thanks.
pg. 15 Step 8:
Although not errata per se, it is rather Windows centric.
If you are on OSX you will not see hello.obj or hello.exe but rather a.out
(or if you used gcc hello.c -o hello hello.c you will see hello.out).
To run hello.out (or a.out) type ./hello.out (or ./a.out) depending.
(I can't speak for Linux OS).
pg. 35 Exercise 5:
line 9 shows fgets(buffer); Your compiler should complain it needs 3 arguments.
line 9 should be fgets ( buffer , 256 , stdin );
pg. 44 Table 3.3:
"Full Name" and "Commonly Used Keyword" labels are switched.
pg 60 Do/Don't list: Under Don't - second Don't 'forward slash' should be 'backslash'.
Don't forget to use a backslash to continue a string of characters onto a second line.
pg 89 Exercise 3: Says to make listing 4.1 count up instead of down, but listing 4.1 already does that.
pg 112 Last Sentence under Recursion: "the factorial of 9 and larger values are outside the allowed
range of integers." This depends on your compiler. Xcode for mac for instance
lists an unsigned integer to be 4 bytes and can handle a factorial up to 12! .
pg 238 Question 10b. answer is shown as 'A' but 10e. is shown as 73. If by values they mean
the integer then 10b. (*string) then should be 65 not 'A' or if by value they mean char, then
10e should be ' I '. Inconsistent.
pg 242 Defining and Declaring. This author mixes and mostly inverts the definition of 'declaration'
and 'definition' of the type struct. As per 'The C Programming Language' by K&R, "The keyword
struct introduces a structure declaration, which is a list of declarations enclosed in braces." Not until
a struct is instantiated is the struct 'defined'. When it is defined, then storage is created and set aside.
pg 257 Line 4 of program. Should have a semi-colon after bracket. };
pg 266 Line 17 of program should be: 17: {4, "Benjamin"},
pg 366 Listing 15.2 %p's should be %lu's. so:
printf("\nThe size of multi = %p", sizeof(multi)); //should be:
printf("\nThe size of multi = %lu", sizeof(multi)); //same for next two lines.
pg 367 5th paragraph: Says "In other words, it's incremented by the size of the object to which it
points." While not an error, it is an ambiguous idea with the previous page that shows 'multi' to be of size 32. So one would think multi + 1 should be pointing to something 32 bytes larger; but it
does not. It points to something 16 bytes larger.
pg 367 Listing 15.3 (all printf's) uses format specifier %u and it should be %p for addresses.
also, 'value' should be 'address' in lines 10 and 11.
Check back often as I go through the book I will update the errata here. If you have any errata yourself, please let me know and I will add it.
Thanks.
pg. 15 Step 8:
Although not errata per se, it is rather Windows centric.
If you are on OSX you will not see hello.obj or hello.exe but rather a.out
(or if you used gcc hello.c -o hello hello.c you will see hello.out).
To run hello.out (or a.out) type ./hello.out (or ./a.out) depending.
(I can't speak for Linux OS).
pg. 35 Exercise 5:
line 9 shows fgets(buffer); Your compiler should complain it needs 3 arguments.
line 9 should be fgets ( buffer , 256 , stdin );
pg. 44 Table 3.3:
"Full Name" and "Commonly Used Keyword" labels are switched.
pg 60 Do/Don't list: Under Don't - second Don't 'forward slash' should be 'backslash'.
Don't forget to use a backslash to continue a string of characters onto a second line.
pg 89 Exercise 3: Says to make listing 4.1 count up instead of down, but listing 4.1 already does that.
pg 112 Last Sentence under Recursion: "the factorial of 9 and larger values are outside the allowed
range of integers." This depends on your compiler. Xcode for mac for instance
lists an unsigned integer to be 4 bytes and can handle a factorial up to 12! .
pg 238 Question 10b. answer is shown as 'A' but 10e. is shown as 73. If by values they mean
the integer then 10b. (*string) then should be 65 not 'A' or if by value they mean char, then
10e should be ' I '. Inconsistent.
pg 242 Defining and Declaring. This author mixes and mostly inverts the definition of 'declaration'
and 'definition' of the type struct. As per 'The C Programming Language' by K&R, "The keyword
struct introduces a structure declaration, which is a list of declarations enclosed in braces." Not until
a struct is instantiated is the struct 'defined'. When it is defined, then storage is created and set aside.
pg 257 Line 4 of program. Should have a semi-colon after bracket. };
pg 266 Line 17 of program should be: 17: {4, "Benjamin"},
pg 366 Listing 15.2 %p's should be %lu's. so:
printf("\nThe size of multi = %p", sizeof(multi)); //should be:
printf("\nThe size of multi = %lu", sizeof(multi)); //same for next two lines.
pg 367 5th paragraph: Says "In other words, it's incremented by the size of the object to which it
points." While not an error, it is an ambiguous idea with the previous page that shows 'multi' to be of size 32. So one would think multi + 1 should be pointing to something 32 bytes larger; but it
does not. It points to something 16 bytes larger.
pg 367 Listing 15.3 (all printf's) uses format specifier %u and it should be %p for addresses.
also, 'value' should be 'address' in lines 10 and 11.
Saturday, September 22, 2012
I Can't Find My Cursor
I'm not stupid. I've done some programming. I'm an electronics technician for over 30 years.
But now that I have my 27" iMac and will soon be adding another monitor, the real estate that one can lose their cursor on is growing.
After a quick search I found five options:
1) Hold Ctrl+Scroll and the screen will zoom into where the mouse is.
2) Move all the way up to the left and click, and the menu will expand showing you where the mouse is.
3) OmniDazzle from omnigroup.com
4) mouseposefrom from Boinx Software
and
5) MouseLocator from 2pointfish software company.
I chose 5. MouseLocator from 2pointfish.
It's easy, download, install (I then keep the .dmg in a folder called 'downloaded software', because it has the uninstaller), then when you lose your mouse, just hit Ctrl + Space (can be changed to anything you want).
This is what I see for the 2 secs that it is set up for:
Works great. No more getting lost in a sea of pixels.
But now that I have my 27" iMac and will soon be adding another monitor, the real estate that one can lose their cursor on is growing.
After a quick search I found five options:
1) Hold Ctrl+Scroll and the screen will zoom into where the mouse is.
2) Move all the way up to the left and click, and the menu will expand showing you where the mouse is.
3) OmniDazzle from omnigroup.com
4) mouseposefrom from Boinx Software
and
5) MouseLocator from 2pointfish software company.
I chose 5. MouseLocator from 2pointfish.
It's easy, download, install (I then keep the .dmg in a folder called 'downloaded software', because it has the uninstaller), then when you lose your mouse, just hit Ctrl + Space (can be changed to anything you want).
This is what I see for the 2 secs that it is set up for:
Works great. No more getting lost in a sea of pixels.
Saturday, July 7, 2012
Microstick II Start Up
I got the Microchip Microstick II and found some things that others may learn from as well.
I started using the Pic32MX250F128b (Microchip left the 'b' off in the parts included list, but the 'b'
version Pic32 is the 28 pin one that comes with the Microchip II).
First, using Microchip MPLAB X IDE the Microstick II was not recognized by the MPLAB (inactive connection).
I had to restart MPLAB X, and replug in the Microstick II into the USB cable.
Using OSX, the directions state a)... b) ... select Starter Kits (PKOB), and then click Apply.
I had to click on the Serial number, then 'Apply' to get it to work.
Second, the code example given must be for MPLAB 8.x as MPLAB X did not recognize that file.
So, just start a new project like it states in the MPLAB X Quick Start guide, then right click on Source Files in the tree and import the BlinkLED.c file from the MPLAB 8.x example files.
Then 'c)' should be: c) Select 'Debug Project' to download and run the project.
Not Run>Run Project. (that must be in 8.x version).
MPLAB X will alert you that you it must disable the watchdog timer to make the program work correctly for this session, hit yes or okay and then your LED will do it's blinking thing.
I started using the Pic32MX250F128b (Microchip left the 'b' off in the parts included list, but the 'b'
version Pic32 is the 28 pin one that comes with the Microchip II).
First, using Microchip MPLAB X IDE the Microstick II was not recognized by the MPLAB (inactive connection).
I had to restart MPLAB X, and replug in the Microstick II into the USB cable.
Using OSX, the directions state a)... b) ... select Starter Kits (PKOB), and then click Apply.
I had to click on the Serial number, then 'Apply' to get it to work.
Second, the code example given must be for MPLAB 8.x as MPLAB X did not recognize that file.
So, just start a new project like it states in the MPLAB X Quick Start guide, then right click on Source Files in the tree and import the BlinkLED.c file from the MPLAB 8.x example files.
Then 'c)' should be: c) Select 'Debug Project' to download and run the project.
Not Run>Run Project. (that must be in 8.x version).
MPLAB X will alert you that you it must disable the watchdog timer to make the program work correctly for this session, hit yes or okay and then your LED will do it's blinking thing.
Subscribe to:
Posts (Atom)