GOD F&%$n' HATES ME!!!

  • Thread starter Thread starter FZfile
  • Start date Start date
FZfile

FZfile

New member
OK.

Emeric
DrStawl
Evildick

you all know what was going on as of yesterday with this ordeal and last we saw......IT WAS WORKING......

....I should have know better.

So......as the files were loading (Step 3 of the Windows Setup and Instalation), I went and let the dog out, got some OJ, watched the weather, ........I was going to hit the bar and have a beer...............but I came back and................

The freakin piece of crap froze again.\

Right in the middle of step 3.

So now I try and reboot and it recognises that installation stopped right in the middle of loading files so it said to "Safe Boot" when the screen came to it.

Except it never did get there.

It would just stop after initializing setup.

I thought maybe it could be the CD Rom but any way I started from total scratch and erased the hard disk, fdisk'd it again and reformatted.

Started with the boot disk and now it tells me that the OS is missing........... :confused: .....no shit!!!!

thats what I'm trying to do.

Should I start over and fdisk (or efdisk) my brand new 40G drive and then IF I can get this OS installed, transfer that partion to the 2.5 disk????????

I am very frustrated.

I appreciate all of your time you guys.
I know I am sucking up more that I should.

I haven't even picked up my damn guitar in 4 days cause of this damn thing.

damn!!
-mike
 
I had a similar problem once. I had to take out the sound card to get it to go all the way.
 
I had the exact same problem. I built a Athlon 1.4 gig system with a 20GB 7200 HD. I changed a couple things before I had success. I took my sound card out and did the Fdisk and reformat stuff, but the best solution was to go to the HD website (in my case it was Western Digital) and download their utility software. It fits onto a floppy and it will correct any glitch in your Hard Drive. I think the OS loading failure has to be with the Hard Drive. This worked for me. Also, you want to make sure you have the right cable going from the HD to the MBoard. When I built the system I very foolishly used my old IDE cable on the ATA Hard Drive and ofcourse that mucked everything up. You may check that. I also removed my sound card until the OS was up and running well, then re-installed it. Good luck
 
Are you using 2 hard drives? I had huge amounts of problems installing win.98, so I went out and bought xp thinking that might help. I was still having installation problems and got worried because I built the computer myself, which I had never done before, and thought I fucked something up.

Here's what helped for me...

Be patient. I kept restarting my computer because I thought the installation or boot up had frozen, when in reality it just took forever (like 45 minutes or more).

I also unhooked my second hard drive, and waited to install it until after the OS was installed because it got confused about which drive letter was correct, and wierd stuff like that.

hope this helps.

josh
 
I would remove all unnecessary components like sound, network, floppy(if not needed for install). Just a HD and CD and start from there. You should be able to set the boot sequence to CDRom first, in your bios, put the CD in the drive, and reboot.
 
Thanks guys.

I had to take a break and actually pick my guitar up and get a decent nights sleep.

I did do those things like unplugging all of the unnecessary componants.
I finally got to a promt so I started over again and erased the drive and re-created a new prime dos partition.

Then changed the BIOS to boot from CD.

From there I formatted the drive from the windows disk and ran set up again.

I got further than ever before. I got about 32% through the file downloading step when I got a SUWIN General Protection Fault Error.

I started over, after trying to just run setup from the CD ( it would not go) and got about 20% through downloading and got a different SUWIN error.

Before, my hanups all happened before i got a progress bar, so at least Im getting a little closer.

I looked up the SUWIN errors ( I dont remember exactly what they were, I'm still at work) and got real general info.

As in......."it could be anything. try something and see what happens".
Which is basically what I did.
I noticed in the BIOS that the RAM / CPU setting was to ASYNCRONOUS and they are both at 100mHZ, so I changed that to SYNCRONOUS.
I turned OFF the Auto Floppy Scan on Boot since I am booting from the CD Rom.

This seemed to speed up the POST and get me to the startup faster but I still cant complete the install.

Any more ideas????????????.

I appreciate all of the help from everyone.

I realize God doesn't hate me, he just doesn't like computers.

-Mike
 
One more quick try

Go back into your BIOS. Set the FSB speed to 100Mhz instead of the 95 that it's currently at. Then drop the CPU multiplier down to 5 instead of 5.5. Before doing this, you may want to return to it's it's Default settings.
 
Thanks...I forgot about the 95 setting

That means, i'm guessing, that i am not truely SYNCRONOUS.

I willl certainly give that a try.

-mike
 
You may have answered this before, but what version BIOS are you running? If you haven't updated it yet, you can get a newer version here.

http://www.jetway.com.tw/evisn/download/bios/index-2.htm#530

I was beginning to wonder if you have a AMD K6-2+ instead of an AMD K6-2. Anyways, after you upgrade the BIOS, it may open the option to set the FSB at 97 and the multiplier at 5.5 like it's supposed to be.

Just look for the file labeled 530BFE08.bin

You'll also need the AwdFlash.exe located at the top of the page.
 
FZfile.

By the sounds of things, you have some major hardware problems.

Installing an OS is not rocket science.

My guess as to the problem components, in this case and order:

Motherboard
RAM

I can't be sure without actually working on it in real-life, but the problems you have are pointing to this, to me. It appears you have everything hooked up correctly, and most common problems have been eliminated.

If you have a computer tech in your local, that you can bring the machine to, do it. Not saying you won't figure this out yourself, but it may save you a lot of time and grief.

Not giving up on your situation, but sometimes problems get so obscure that standard swapping of components is involved, and that is tricky to do unless you have known good components. Even trickier via internet communication.

Let me know how it goes.
 
GOD hates me

GOD loves you , you just have to love yourself and love GOD back.
 
Has there ever been a functional computer with a K6-2?

"GOOOOD HATES US AAAAAALL"
- Slayer
 
Thanks....about BIOS flashing.

It says on the READ THIS FIRST BEFORE FLASHING BIOS page of the link you sent Evil that I need to make a boot disk.

I can already boot to a C:> promt.

Can I just go to a:
and run AwdFlash.exe from there??????

...or do I need to make a boot disk with Awdflash and the.bin file on it and ONLY boot from that????


Emeric.....I am going to ignore what you say for now because I am thinking you could be right.
But my BIOS are only v.1.0A so maybe the update will help.
I know the manual only lists it to run a 450 CPU max but the Jetway site says that my chip has been run succesfully and even overclocked w/ no problem.

BTW how do the SiS chipsets compare to other chipsets????
I know people have had problems with Via chipsets and audio apps.

Meshuggah, are you saying the K6-2 is un-smurfy?????

-mike
 
To do it the easy way, go here :

http://www.viahardware.com/faq/kt7/kt7faq.htm

Scroll down to the bottom of the page and download DRDFLASH.EXE. This is pretty much a hands off program that makes a boot floppy. Then copy both awdflash.exe and your .bin file to the floppy.

When you boot up into DOS, go to A:/
type awdflash.exe
type in the name of your .bin file
save your old .bin file when asked just in case this doesn't work
Flash your BIOS.

Remove floppy and start up your computer, enter the BIOS to see if you notice any changes. Right when it boots up, you'll see the BIOS string at the bottom of the screen. Check to make sure it reflects the new BIOS rev.
 
Sometimes bad RAM will cause wierd problems like that. If you have more than one Ram module, try one, and then the other, to see if you have the same problems with each. If it works with one and not the other, you have a bad RAM chip.
 
You must log in or register to reply here.
Back
Top