I picked this up from an article in the Toronto Star.
New guidelines have been released regarding the treatment and prevention of life-threatening allergic reactions. They can be found at allergysafecommunities.ca and highlight that:
Epinephrine is the first line medication that should be used in the emergency management of a person having a potentially life-threatening allergic reaction. (Not antihistimines or asthma medication).
I hope that none of us ever need to use this information.
Tuesday, 28 February 2006
Monday, 27 February 2006
Sunday, 26 February 2006
Saturday, 25 February 2006
Tech Troubles: Transferring mdb file from one XP box to another
Instead of spending my time doing something productive, I've been wasting it trying to trouble-shoot this annoying problem.
I have 2 machines in front of me (System A and System B) both running XP Pro. They are connected through a local area network. They both have shared folders with wide open permissions and can see each other.
I can copy txt, pdf, doc, jpg, psd, gif, html and most xls files from System A to System B (and vice versa) without issue (files transfer quickly and effortlessly).
However, when I try to copy across an mdb file from System A to System B, things grind to a halt. 1MB files which should fly across, state in the copy status box, that it will take a total of 9 minutes to complete the transfer. And then, of course, the transfer fails ungracefully. (No, the mdb files aren't in use, either).
It almost looks like something on System B is scanning the mdb to see if it's dangerous and then preventing it from coming across when it can't be sure it's safe. However, when I borrow a USB drive, I can copy the mdb onto the drive from System A and then from the USB drive to System B without issue. So it's not an obvious System B thing. (Although I can copy effortlessly from B to A, so it's something to do with System B). It doesn't seem to matter whether I'm pushing from A or pulling from B.
A quick Google search reveals these articles: which prove that I'm not alone, but other than that, don't really help. I tried to e-mail the poster (Karl Irvin) but alas, his e-mail address is no longer valid. (Mr. Irvin, if you're out there... did you ever get this issue resolved?)
If any of you out there have any thoughts on this matter, I'd love to hear from you!
----------------------------
Additional info:
I have 2 machines in front of me (System A and System B) both running XP Pro. They are connected through a local area network. They both have shared folders with wide open permissions and can see each other.
I can copy txt, pdf, doc, jpg, psd, gif, html and most xls files from System A to System B (and vice versa) without issue (files transfer quickly and effortlessly).
However, when I try to copy across an mdb file from System A to System B, things grind to a halt. 1MB files which should fly across, state in the copy status box, that it will take a total of 9 minutes to complete the transfer. And then, of course, the transfer fails ungracefully. (No, the mdb files aren't in use, either).
It almost looks like something on System B is scanning the mdb to see if it's dangerous and then preventing it from coming across when it can't be sure it's safe. However, when I borrow a USB drive, I can copy the mdb onto the drive from System A and then from the USB drive to System B without issue. So it's not an obvious System B thing. (Although I can copy effortlessly from B to A, so it's something to do with System B). It doesn't seem to matter whether I'm pushing from A or pulling from B.
A quick Google search reveals these articles: which prove that I'm not alone, but other than that, don't really help. I tried to e-mail the poster (Karl Irvin) but alas, his e-mail address is no longer valid. (Mr. Irvin, if you're out there... did you ever get this issue resolved?)
If any of you out there have any thoughts on this matter, I'd love to hear from you!
----------------------------
Additional info:
- Rename foo.mdb to foo.jpg before copying it doesn't work when copying with xcopy or Explorer.
- Copy foo.mdb via the command line instead of Explorer doesn't work. It just times out.
- pkzip foo.mdb allows me to copy the file over just fine.
- I can copy mdb files from A to C and back again without issue. However, I can't pull the mdb file from C to B.
- This applies to ALL mdb files I've tried. (And one XLS)
- I don't think that the file is corrupted or on a soft spot on the disk. I've copied the file on the original disk to another folder (the original file remaining where it was) which should counter for that. I the fact I can copy from System A to USB drive would mean it's not a System A disk issue. And that I can copy other types of files to System B would mean that it isn't System B's disk.
- System B is running Norton Firewall and Antivirus. Both shut off at the application level and the service level.
- According to Task Manager on B when you trying to copy from A to B, SYSTEM IDLE PROCESS sucks up over 95% of the CPU. And then leaves me with a "network connection lost" error. (Which doesn't occur when I'm moving other files).
Friday, 24 February 2006
Thursday, 23 February 2006
Wednesday, 22 February 2006
Tuesday, 21 February 2006
Monday, 20 February 2006
Baby-sign: unexpected advantage
When mommy has laryngitis, the family can still communicate! (more or less)
Friday, 17 February 2006
QOTD: Fathers
Send this one out to all the daddies you know ....
The most important thing a father can do for his children is to love their mother.
- Theodore Hesburgh
The most important thing a father can do for his children is to love their mother.
- Theodore Hesburgh
Thursday, 16 February 2006
Subscribe to:
Posts (Atom)
