The fans keep going. Zippy isn’t my machine, so I’m not entirely bothered. but it’s a proven fact that air circulation prevents stuff like this happening. Except Zippy doesn’t *have* air circulation. I’m amazed it’s survived as long as it has to be honest.
Following on from the suspected dead RAM in Zippy, it had been sat there, waiting to be tested in another machine. And, as today was a boring Sunday afternoon, I decided to kill two birds with one stone. Firstly, test the RAM using the PVR box, then actually get the PVR box working.
So, I removed the 512Mb stick in there, and replaced it with the two suspect ones from Zippy. Indeed, MemTest flagged up errors after a few minutes….
(Image lost)
So, the next step was, obviously, power of deduction. I removed one stick, and within a few minutes, Memtest did indeed pick up RAM errors.
So, the faulty stick was removed, and disposed of.
(Image lost)
The other test passed fine, so it was kept.
SO, then onto the PVR box itself. Could I get it working? Firstly, I decided that after all of the changes I’d made, it would be best to start from the beginning. Off went the partitions, and a shiny new set were created. Exactly why it takes Windoze almost an hour to partition and format a new drive, yet it takes Linux less than a minute, remains a mystery to me.
Either way, the software was installed. And after pissing around with the settings for a bit (sadly, I don;t know exactly what I did), it displayed an image! OK, so it was nothing but snow, but finally we had an image. It picked up on the tuner, but if anything, it was going to be used with composite input so I could use it with the digibox.
Unfortunately, the digibox was unavailable. Bugger. What else did I have to hand with a composite output? Yes, you guessed it. Up steps the trusty XBox Of Glory. Hurrah!
So I connected it, ran the set up program to change the active device to Composite-0, and…… nothing. Got lots of audio. But no picture. Sigh. It must be on one of the other 5 composite channels. I have no idea why there’s 5. There’s only one yellow socket on the back. There’s the S-Video socket, but that has its own channel.
Now, either due to a limitation of the software, or my lack of knowledge, each time I needed to change the composite channel, I also needed to reboot.
So imagine my amusement when I got to Composite-3, and still had nothing on screen. With one last selection to choose, I wasn’t holding out much hope. So, One change and one reboot later, it all came down to the last choice. Composite-4. I held my breath while I rebooted. Would it work? COULD it work?
The answer is yes. I let out an almighty roar of delight, as the Xbox logo flashed across the screen.
(Image lost)
So, at the minute it’s “working”. It accepted input from my XBox, and allowed me to pause it, as shown in the picture. I’ve yet to record anything properley using it.
My findings are…
- The Processor and chip might be too slow It looks as if it needs a *beast* of a machine. It’s a 1.2ghz Athlon running at 100Mhz FSB, with 512MB of memory. The memory seems to be enough, but the processor is certainly casing issues
- Hardware MPEG encoding/decoding is a definite advantage. My card only does one of these, and I can’t remember which :)
- Disk space = paramount. There’s a 120Gb drive in there currently, so that’s not too bad I suppose. But more will be better. Even better would be putting a DVD writer in there. I’ll look into it.
- DVD decoding/storing doesn’t work. And I’m going to leave it like that, for obvious reasons!
- It has MAME in it! Get MAME working
- Get TV Output working. The instructions given don’t work.
Updates on it, once again, when and where appropriate
Zippy’s been to hell and back.
Random crashing over the last few weeks. I wasn’t aware of it, due to the fact it’s not really my machine.
It was put down to Windows ME being shit. So it was decided that it was time for XP to be installed. And while backing up it kept crashing.
The information on it was pretty much backed up anyway, so it was wiped during the XP install. Except it kept crashing at 56% of transferring the files from the XP disk. This is an original CD as well, so exactly why it did it was beyond me.
Suspecting a disk problem, I backed up the disk on Beastbits. No errors while copying it. It can’t have been the media. The backup did exactly the same thing too.
I went to work, trying to figure out the problem. Came home this morning and ran Memtest. And oh-my-god, it lit up like a fruit machine. So, the memory was replaced, and the installation retried. Got past copying the files. But, during the install, this error appeared…
(Image deleted)
Full format, reinstall later, everything appeared fine, except it would crash when starting Windows in normal mode. Monitor would go into Standby or show “Out of Range”.
Turned the memory timing down to 100Mhz (even though they’re supposed to be 133’s) and everything now appears fine. Updates if and when needed.
The DVD writer in Beastbits has finally died. At least I assume it’s died. And when things go wrong like this, the best cure I’ve found is to throw a credit card at it.
DVD writers have dropped in price considerably, since I bought that one in 2003. It paid for itself when my original 120Gb HDD almost gave up the ghost. Can’t think of a thing I lost, thanks to that.
Either way, I’ll be going for a retail model, in the hope of getting some decent writing software. Decent, in the sense it’s something other than crap like Nero Express.
The overheating situation with Beastbits is still there. 2.2Ghz worth of machine, and I can hardly use it. The fan/heatsink looks chock full of dust, so when I remember, I’ll blast it with some compressed air. If it still crashes, THEN I’ll replace the heatsink.
Thankfully, everything else this year has been stable, touchwood. Bungle needs a reboot, and an fsck. Getting “Disk Full” messages, when it’s not even close to full. Loving his uptime though…
3:42am up 74 days, 14:32, 1 user, load average: 0.07, 0.05, 0.01
Something started happening with Beastbits a couple of days ago - I would be platying MAME, and the machine would just BSOD on me. It only seemed to happen in MAME, so I decided I just had a faulty install, or whatever.
For some reason, I decided to load it up, and noticed a few things. First off, is that when it BSOD’d, this time, it was giving different .sys files each time as faulty. First was something to do with USB. So, I unplugged all of my USB devices, and rebooted. Still blue-screening, but a different file…
And it didn’t appear to be doing anything in particular when it BSOD’d.
So…I checked in the BIOS. It can’t be my machine overheating………. could it?
(Image lost)
Total Posts 849
Total Comments 502.