dbminter

Moved post to where it belongs.

Still, apothecary table is a bit more modern than materia medica table.

A CMC gun would be a Triffid gun. Actually, CMC discs might make pretty good ammunition for a disc firing gun.

Now, Prime is a Double Convoy, truckin' through the night! Yeah, Prime is a Double Convoy; got a Destron in his sight!

Then again, what in life is?

I'd forgotten David Tennant had already been in Doctor Who before! Back for Big Finish Productions.

Ha! Never thought of that! It seemed pretty small though when the Dr and the gang were in there though. What I always thought was most interesting. WHY is there a human sized entry hole in the top of the shuttle? I could understand one Dalek sized, since the Dalek that operates the shuttle is apparently attached to the controls, like in the Absolam Daak stories from the magazine strips. That way, an operator would be inserted or removed and then automatically connected. So, why is there that equally human sized elevator shaft behind the control Dalek? IF there was an elevator for a Dalek to come up, then, why didn't the Doctor bring it up? The answer is probably the budget.

Well, DID you? No did a reformat instead....... STILL formatting?

As for the term chemist, at least apothecary has fallen out of fashion.

Looks like volvo's got himself... a CONVOY! Truckin' through the night!

Wait, wasn't there like a big terrorist arrest there recently, too? And a war somewhere over there in Israel?

Exactly. If you're going to use it, best to turn AutoStart or whatever that option is to load on Windows start and set it to off.

Sorry, don't have the image file anymore. I could try to image the disc and then try to burn that new image to a DVD+RW and see.

Was burning an image to a DVD+RW when the Topic error message came up at the start of Verify. I've never seen it before, but, it probably has a reasonable explanation. The image was a CD sized one that I was burning to DVD purposefully. I've done this before, burning CD sized data images to DVD for testing things like bootable discs, etc. But, this is the first time I've ever come across this dialog. But, I am guess that is what it means? That the file data type was CD, given its size of about 785 MB, and the device data type was DVD+RW, based on the disc present in the device?

Lucky you! Kind of like how on the 2005 season of Doctor Who. Russell T. Davies took nearly every opportunity he could to slam Cardiff for some reason.

Yeah, I know what you meant. The bridge chip. We've had more than a fair share of bridge posts with those bloody ALI's and semaphore time outs.

I don't know the chip set in the first drive. Never opened it. The 2nd one I opened but didn't think to check. It may be NEC, BUT I could just be transposing the chip that was on the PCI card that didn't work. However, opening the drive to check, should I ever need to, is relatively easy.

Maybe it's actually lfcrule5 instead. That ye olde lfcrule is really ye olde, 1972 years old. And this newbie is a newbie quite literally: 5 years old. But, quite a literate 5 year old.

If I'm getting 28,xxx KB/s, then, that should be roughly equivalent to 28 MB/s. CONSISTENCY, PEOPLE! So, that seems to be on par with what USB 2 should be. The slow speeds appear to be caused by that one weird case that happens with the 2nd drive, but, not with the first. Either because of the design, construction, or configuration of the HD in the enclosure or the enclosure itself. Because it only happens when the drive is powered off and then back on.

Yeah, 26,xxx instead of 26. Typed in anger.

Okay, rebooted, checked the I/O's on drives 1 and 2, powered off drive 1, powered it back on, rechecked the I/O, and got the same value as before. Powered off drive 2, powered it back on, checked the I/O, and, as expected, the I/O plumetted. Checked the I/O on drive 1, and, strangely, as I expected drive 1's I/O did NOT change. Without rebooting, turned off drive 1, turned it back on, rechecked the I/O, and it had not changed! Checked the I/O on drive 2 again, and, it was the expected still lesser value. So, the conclusion is that something in drive 2 causes this effect ONLY if it is NOT the only attached drive and ONLY if it has been powered off/powered back on or disconnected/reconnected. Which means for drive 2, I need to remember to reboot IF I ever have to turn it off/disconnect it and turn it on/reconnect it. I wonder if the same process repeats if I connect one drive to the front and another to the back? I wonder if it repeats if I use Safely Remove Hardware first... time to get to work! It DOES repeat if I Safely Remove first AND power off and power on. It does NOT repeat if I Safely Remove and disconnect and reconnect the drive. Time to test just disconnecting and reconnecting. It's only with the drive powered off and on, it seems. Even without Safely Remove, disconnecting and reconnecting the data cable did not cause the problem. And, the last test. If the drive is powered off at any point and powered on, the system MUST be rebooted to restore the full write speed. Just logging off and back on did NOT help. I also wonder what it is about the 2nd drive that causes this phenomenon... something in the bridge? ALI?! Or the drive in the enclosure itself? DAMN! I had the drive opened up the other night! I should have checked the chip when I was able to look at it. Oh, well, at least, once I got rid of the screw that WOULDN'T come out without pliers... the drive is easily reopened for future examination.

Okay, I think I finally have some "SENSE" of this damn problem. There's something happening that I cannot explain its reason, but, it's the cause. There ARE two different speeds being reported by the 2nd USB drive. Whenever the 2nd drive is connected/powered on for the first time, it behaves "normally" writing an image file in Build mode at about 11x. Whenever this drive is the ONLY one connected, it can be powered off/disconnected and reconnected without problem. BUT, if the drive is connected WITH the other USB 2 HD, THEN something interesting happens. Disconnecting the 2nd drive or powering it off and reconnecting it/powering it on causes the slow speed thing. The write rate drops to about 4x instead, or about 1/3. WHY this happens... Did a quick test with this in HDD Tools. The I/O Rate plunges from 27,xxx KB/s to 9xx KB/s. Need to reboot and see if this process repeats on the first drive. IF it doesn't, then, it seems to backup, FINALLY a conclusion of mine through all this silly process!

Another joke that writes itself! Check out the title of this page, from an Icelandic museum devoted to various aspects of the penis of multiple animals. http://www.phallus.is/megin.php?tunga=en&val=3

Good! I am still puzzled by at least one thing, though. What is causing that Hi-Speed device connected to a slow speed port message?

Now, more importantly... how confident are you that your USB 2 HD is running at Hi-Speed?