Sunday, March 23, 2014

actually, i had connected my floppy cable upside down in the process of swapping drives around, which is why the light was solid :|. put in the right way, there seems to be no power to the drive at all. no seek from the boot block. bricked...

reason: there's no power to the board. hotwiring it isn't going to get the read info. shorting things would only be useful if it's not reading from boot block at all, which i'm not convinced is it.

see, i may have two damaged drives. the pins on both are bent all around. in contrast, the cd-r powers up, through ide or through sata. i'm not convinced it's reading anything, especially through sata, but it spins and flashes and turns the fan on and stops. it doesn't seem to matter what disc is put in...so that seems more like firmware...

...but it powers up. neither floppy does.

i've also determined that at least one of the floppies i was using is unstable. i could have several bad floppies. the copy operation seems fine for about ten minutes, then seems to evaporate. like, i'll do a format /u and copy the rom over and three hours later will get read errors on that disk in that drive.

it's tedious, and i don't think it's the problem, but i have to determine the integrity of the floppy disks before i give up on this approach.

i then have to try every cd-r/cable combo i have.

however, i am currently resigned to reprogramming the chip.
http://www.oocities.org/rrbhaius/recoverbios.pdf

i suppose i could still try some older roms.

the floppies could be damaged.

but i don't seem to be getting read/write access.

i mean, the light is on. and it spins. but it's not reading.

it's a better idea every single one than to short. so, here i go on that...

i mean, it seems like they're perfectly describing the situation....
yeah, that still doesn't turn the power on the mobo on. i wasn't sure if usb needed it the same way the older connections do. apparently, so.

i can't see how a drive would work where a hub doesn't. so, i'm leaning more and more towards shorting.
actually, my hub has a power in. i don't use it, but....hrmmn....let me test this, anyways, see if i learn anything from it.
precisely whether the short works or not depends on if the information needed to get power (rather than instructions) to the peripheral i/os on the board is accessible somewhere outside the bios (proper), which the proposed recovery process (through boot block) suggests is actually the case. otherwise, i can short it all day without accessing the power info in the bios that doesn't exist.
nope.

i'm not getting any power to the board past a certain point, which is a different problem than i dealt with the last time i did this. see, but it's a bit deceptive, because the externals all take power from the psu. so, the cd spins when you put something in it and the floppy lights up, but neither are able to communicate with the cpu, so the emergency bit doesn't come in.

one of the things that made me understand what's happening a little bit better was plugging an mp3 player into usb. i wasn't expecting power from the board, but i was hoping the power on the key would be enough to get over the hurdle. unfortunately, the key is programmed to turn off on the physical connection, rather than an electronic one. so, no good.

that leaves me with three remaining options:

a) i can try and short the chip, but i think this is unlikely to work.

b) a better idea is to try an externally powered usb connection. and, thinking back, i think that might have been what i did last time, too. i need an external usb drive for two other reasons now so it will be top priority next monday...

c) i can try and use a jumper to replace the bios. i'm going to have to wait until monday for this, too. it's an excuse to get the soldering iron that i probably should have inherited but, for whatever reason, didn't.

so, my gst money on the 5th is basically going to computer repair. that's mildly irritating, but ok. i don't budget that. it's all stuff i should have around, anyways.

i'm not going to short the chip unless i can find a precise set of instructions. see, i don't think the boot block isn't kicking in, i think the board needs power to communicate with the devices. the short might reset the power along with the force, which shouldn't be missing in the first place, but it's not the intent of the process, so i'm a little cautious about messing with it. as it is, i have no keyboard commands, because there's no power. i have no video out because there's no power. yet the fans are all spinning so it's clearly that the bios crashed before that point...

if i can get some power to the board, i think it should go into recovery and flash off of any media it can read. but, i need to be careful with that.

i could do this with a screwdriver, and conceivably have it up in a few hours. in the back of my mind, though, i'm thinking that, if i wait, and the usb trick works, it won't be necessary - and that the jumper is a safer way to force it. it's simplicity v. safety...

if i can find exact instructions, i will do this. if not, i'll wait for at least the external usb.

there's always reading to catch up on.
actually, i'm realizing the emergency iso i downloaded doesn't have the right file. i have to try that...
yup. i've tried every possible combination and the boot block is just not setting in like it should. i'm rather confused, though. that should be there.

i'm going to have to wait a few days before i can get the materials for a jumper.
the floppy isn't doing what it's supposed to, and the cd isn't either. the flash shouldn't have fucked my boot block, but i'm not even getting beeps with no ram.

so, it's looking like i'm going to have to jumper this. ugh.
it was indeed one bad bios, along with at least one drive of questionable integrity, and i'm irritated i spent so much time with it. there wasn't a way to reset the cmos, but a "set to default" got the floppy working properly in freedos. sort of. it's still sketchy. i'm going to have to flash...

first, to find a disk that i can actually format. i'm confident that this should get the main pc's bios in.
well, i found a bios, and i can't see how one version of dos is really better than the next...

there doesn't appear to be a way to clear the cmos, besides "shorting" it. like i want to do that...
so, dumbass move #2 this month was flashing my bios. i thought it would be a good idea, moving up to 64-bit. my recording machine has been unable to post since friday evening.

a stuck bios chip is not an irresolvable problem, in theory. these particular chips have something built into the firmware that checks the floppy drive. there's also a cd utility i've used before, but cannot locate right now. i'm hoping the floppy works.....

...but i've been having difficulty finding an operating system that will read a floppy drive. there's a known issue with xp (the workaround is to use server 2003, because home users shouldn't need floppies, apparently). my copy of 98 is broken, in general, and won't read it either. i've tried three specialized recovery linux live cds that won't mount...

so, i'm resorting to installing freedos. and then real dos, if that doesn't work.

worst case scenario, i'll have to go in with a parallel cable and reprogram it manually. so, there's a few more days lost....

i know the drive works and the discs are good, if for no other reason than that i just installed 98 with a boot floppy (even though the os won't read, and it won't read from funny windows 98 dos).

so, i either have two bad floppy cables, two bad floppy drives or one bad bios. i can't get the floppy to do anything at all on this backup motherboard.

the bios hasn't been flashed since 1999. i doubt it supports any method besides a floppy flash. ironically. nor do i suspect asus still has bioses for this thing around...