print_r($recent);

Array
(
 [545]=>Collections
 [544]=>Good morning
 [543]=>You know the fee...
 [542]=>Date more, care ...
 [541]=>Moving On
)

 

RAMCal(date('my'));

April 2005
sun mon tue wed thu fri sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
             
archives(RAM);


print_r($newStuff);

Array
(
 [RAndoMness]=> 28Sep09
 [JPsDocs] => 22Feb09
 [JPics] => 10Dec11
 [frontpage]
 [FeedBack]
)

recent music
Boycott SONY

print_r($background);
Array
(
 [today]=>
 [past]=>backgrounds
)


getentries(04Dec04);   getentries(04Dec04);

printentries(16Apr05);

All set, as it were
added Sat April 16 2005 at 3:55 PM
1 comments
As they say here in Connecticut, I'm all set. The title's for you guys, Eric and Steve.

At any rate, I am ready for the plug to be pulled on David's server. For two-three weeks, a replacement site will show up, where I can keep everybody posted on my life. Unfortunately, I will not be maintaining JPics, JPsDocs, or any archiving or searching capabilities during the blackout period. The archiving and searching depends completely on the MySQL database that I will *not* have access to, and JPics would require me to be able to upload pictures. Not that I've been good at uploading my pictures in the past month, but it sounds like the uploading process may be further complicated (and space somewhat restricted). Let's be honest- JPsDocs hasn't been properly maintained for quite some time now, anyway.

Absolutely no promises because I won't have a ready test server over the next few weeks, but perhaps I'll take this downtime as an excuse to resurface my site. Even if I can't try out new PHP stuff, I can at least put together some mean javascript and a good looking styesheet. 15 months is entirely too long for a web developer to keep with the same design.

I speak *American*
added Sat April 16 2005 at 6:54 PM
0 comments

Your Linguistic Profile:

75% General American English
15% Yankee
10% Upper Midwestern
0% Dixie
0% Midwestern




There's more to read. Read the extended entry.

Print screen key doesn't work on Microsoft Keyboard?
added Sat April 16 2005 at 8:40 PM
4 comments
Well, actually it does, but I'm getting a bit ahead of myself.

I was trying to get some screen captures, and I couldn't manage to get it to work. I tried pushing every combination of keys I could think of: Shift+Prt Scr, Alt+Prt Scr, Alt+Shfit+Ctrl+Prt Scr, etc. I opened various image editing and word processing tools to make sure that the problem wasn't with the pasting of the image.Then I started hitting up Google.
Unforunately, the complaint that the Print Screen button doesn't work closely mirrors a novice question of what the print screen button (PrtScn, Prnt Scr, or other abbreviations) is actually supposed to do. I *know* that it doesn't send anything to my printer, but I want to know why it's not working.I tried a variety of search terms, when I finally came across the root of the problem in a forum giving reviews of various hardware. Sorry, I don't have the link to give proper credit.

It appears that the problem doesn't stem from the print screen key directly, but rather another annoying "feature" of the keyboard: the F-Lock key. If F-Lock is "On," the print screen key is disabled. Forgive me for not noticing (in the dark) that on the side of the Print Screen key, it says "Insert." Apparently, when the F-Lock is on, the Print Screen key becomes the Insert key.



There's more to read. Read the extended entry.