Buffistas

I could squeeze you until you popped like warm champagne, and you'd beg me to hurt you just a little bit more.

Fuffy ,'Storyteller'

Buffistechnology 3: "Press Some Buttons, See What Happens."

Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!

First Previous Next Last Recent

Gudanov - Oct 16, 2015 2:46:35 pm PDT #24629 of 25496

Coding and Sleeping

I killed the thread with Linux. Sorry.

For fun go to your command line and issue the trace route command for the domain name 'bad.horse', upping the max hops to 60 or so.

Linux> traceroute -m 60 bad.horse

Windows> tracert -h 60 bad.horse

Mac> traceroute -m 60 bad.horse

Then wait for it... I love geeks.

tommyrot - Oct 16, 2015 3:02:34 pm PDT #24630 of 25496

Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.

Aww...

dcp - Oct 16, 2015 3:21:57 pm PDT #24631 of 25496

The more I learn, the more I realize how little I know.

Hah.

DXMachina - Oct 16, 2015 5:31:48 pm PDT #24632 of 25496

You always do this. We get tipsy, and you take advantage of my love of the scientific method.

Hah, indeed.

So, I've got something weird happening on my media machine. It's a six year old Win 7 machine that I set up a year and a half ago with an SSD boot drive and two large hard drives. Today when I went to boot it up, I got a "Loading Windows XP" splash screen, then a blue screen o' death followed by an instant reboot. Multiple reboots produce variations of the same thing. The thing is, the Win 7 installation was wasn't an upgrade. There shouldn't be any Win XP boot detritus, right?

I filmed one of the boot failures to capture the BSOD as it zipped by, but it was generic message, without any error info. I suspect that it must be a problem with the SSD, but it's showing up in the post sequence.

I tried doing a repair from an install disk, but no joy. I'm still getting the same routine. Any thoughts?

DCJensen - Oct 16, 2015 5:44:57 pm PDT #24633 of 25496

All is well that ends in pizza.

For fun go to your command line and issue the trace route command for the domain name 'bad.horse'

I will be posting this elsewhere...

meara - Oct 16, 2015 11:02:05 pm PDT #24634 of 25496

meara - Oct 16, 2015 11:02:45 pm PDT #24635 of 25496

I have zero Windows help, but hi DX!!

DXMachina - Oct 17, 2015 3:34:53 am PDT #24636 of 25496

You always do this. We get tipsy, and you take advantage of my love of the scientific method.

Hi meara!

DXMachina - Oct 17, 2015 7:01:55 am PDT #24637 of 25496

You always do this. We get tipsy, and you take advantage of my love of the scientific method.

So, this morning I started diagnosing, after first checking to make sure that it still was booting to an XP splash screen. It was. So I opened up the box and started disconnecting things to try to isolate the bad actor. I disconnected the two storage drives, then booted up with just the SSD, and lo, there was a Win 7 splash screen and then the desktop a few seconds later. Knowing the SSD was good, I then reconnected the 3 TB media drive, and that worked. So I figured that it must be the last drive (500 GB) that was problematic. But when I reconnected that one, it worked, too. WTF?!?

The upshot is that the machine is working again simply by virtue of unplugging and replugging two hard drives, which makes little sense. This is why I hate computers.

It wasn't all for nought. I'd picked up a 4 TB drive a little while back for an upgrade, so as long as the machine is opened up, I might as well install it.

Jon B. - Oct 18, 2015 5:11:05 pm PDT #24638 of 25496

A turkey in every toilet -- only in America!

DX -- In case the problem ever happens again -- is the SSD boot drive plugged into the lowest numbered SATA port? I had lots of trouble successfully booting my PC until I rearranged the plugs so that the booting SSD was plugged into SATA slot #1.

First Previous Next Last Recent