New Posts  All Forums:Forum Nav:

Blind Flashing and You - Page 6

post #101 of 234
6/28/07 at 3:14pm
Will do, thank you for your help.

Oh, um, I just thought of something last night. I know before I did my flash, I uninstalled my vid-card drivers since I was going to update with new ones from laptopvid2go after the flash. Do you think the fact that my vid drivers aren't currently installed would affect anything?
Reply
Reply
post #102 of 234
7/8/07 at 4:43pm
Thread Starter 
Oh, didnt know you edited your post. The video card drivers are just a way for your operating system to access the resources of your gpu. What we are doing with the videocard bios is controlling what those drivers would access. Hence we are performing low-level "modding" independent of the drivers.

Short answer: No.
Reply
Reply
post #103 of 234
7/23/07 at 7:30pm
Posting in this thread as requested. I think I probably killed the video card as well. I'm not sure if the num/caps/scroll locks cycle when it flashes; It usually takes an hour or so for it to do it, and I'm either not looking at it or not near enough to it to see it in time, unless the cycling is something that keeps happening.

In any case, the only constant is the numlight LED comes on and stays on after a while. Then I'll get two beeps out of it, and nothing happens.

Read through and I'm in the same boat as Ensui, almost exactly. I'll do the commands you gave him with output.txt files.
Reply
Reply
post #104 of 234
7/23/07 at 8:04pm
Thread Starter 
Sounds recoverable as it is performing just like my defunct 6800 ultra. Just tell me which autoexec you are tried/are gonna try.
Reply
Reply
post #105 of 234
7/23/07 at 8:41pm
nvflash -r
nvflash --list > output1.txt
nvflash -c > output2.txt
nvflash -b diag.rom
nvflash -k diag.rom > output3.txt
nvflash -4 -5 -6 -A -y temp.rom
del temp.rom

Going to try that, and paste the txt stuff here so someone better at this than I can interpret

Uh oh, page 8
Reply
Reply
post #106 of 234
7/23/07 at 9:27pm
When it beeps twice, that's to let me know I can remove the drive and restart / turn off the laptop, yes?

Err, actually, what does diag.rom refer to in
nvflash -r
nvflash --list > output1.txt
nvflash -c > output2.txt
nvflash -b diag.rom
nvflash -k diag.rom > output3.txt
nvflash -4 -5 -6 -A -y temp.rom
del temp.rom

I'm assuming it backs up the rom from the laptop you're flashing and outputs a diagnostic txt file. Anyway, I ran that with temp.rom as "reg.rom," corresponding files renamed as well. It didn't output any text files to the drive, and it's the same as before.
Reply
Reply
post #107 of 234
7/23/07 at 9:59pm
Thread Starter 
Sorry, you reminded me I needed to refresh my dos batch programming so as not to have to toy around with nvflash so much. Anyway, that autoexec does have a flaw but it WONT affect whether your card is flashed or not. It would only affect how many times your card was flashed if it was recovered. Anyway, the code should have been: (provided you call your functioning copy of the bios temp.rom)
Code:
nvflash -r
nvflash --list > output1.txt
nvflash -c > output2.txt
nvflash -b diag.rom
nvflash -k diag.rom > output3.txt
nvflash -4 -5 -6 -A temp.rom
del temp.rom
nvflash -y
It would be less sloppy to call another batch file to do the flashing but ah, I'll keep it simple.
Reply
Reply
post #108 of 234
7/24/07 at 12:47am
Well, I did everything to the letter, and it didn't output any text files. Flashing also didn't work. Pretty sure I'm screwed.
Reply
Reply
post #109 of 234
7/24/07 at 1:51am
Thread Starter 
You said you were hearing beeps earlier (after prolonged periods of time). That means you should get output files since your laptop is booting. I don't really know what to say other than that.

Also, when you have a bad flash the best thing to do before proceeding is getting yourself organized with the right bios. Don't just go wandering around the net for any old bios as you may make the situation worse.
Reply
Reply
post #110 of 234
7/24/07 at 3:00am
Right, I know I should be getting them, but I'm not. Since the beeps let you know the flash is complete, and the flash runs after the diagnostics in the autoexec.bat, I should be getting .txt files on the flashdrive, but I'm not. Don't know why. I only tried two different ROM files - the one from MKVtech, and yours. EDIT: I tried the flashdrive with only the output commands, no flashing involved. After an hour or two, it beeped, and the flash drive still has no .txt's on it. Why would it beep, even though I didn't have it set to flash? These are the commands that were in the autoexec.bat
Code:
nvflash -r
nvflash --list > output1.txt
nvflash -c > output2.txt
nvflash -b diag.rom
nvflash -k diag.rom > output3.txt
Reply
Reply
post #111 of 234
7/24/07 at 5:00pm
Thread Starter 
It doesnt matter whether you leave the flashing process out or not. The autoexec will continue to run the commands. Anyway, the program beeps for a variety of reasons. It beeps three times if it cant find the rom I believe and two times if it cant perform the operation. Then it has the really slow two beeps to signify its flashing.

nvflash --list is perhaps the most important diagnostic command but I frankly dont know whats going on with your setup. The lack of file output means the system is not running the autoexec but that doesnt go along with you hearing beeping at all.

I mean this seems completely pointless but you could run an autoexec with just 'nvflash --list > out.txt' and 'del autoexec.bat' ....
Reply
Reply
post #112 of 234
7/24/07 at 5:44pm
It's two successive beeps, rather fast. I guess that means it's not doing anything and I've been wasting my time and yours
Reply
Reply
post #113 of 234
7/25/07 at 12:19am
Thread Starter 
Not exactly. Even if nvflash fails, it typically writes its version number in the output file. You should probably use some other commands to verify bootup to the flash drive....such as dir > out.txt or something like that
Reply
Reply
post #114 of 234
7/27/07 at 5:49am
As I said in another thread it's VITAL that you be at the DOS prompt.
So as ZZ has just said do a dir >dir.txt to confirm you are actually at the command prompt.
Once confirmed there is still hope.
If not then you are pretty well buggered.
Reply
Reply
post #115 of 234
7/27/07 at 6:45pm
I did that, it didn't work. I am, as you so eloquently put it, buggered.
Reply
Reply
post #116 of 234
7/28/07 at 4:53am
Yes, this means you are not getting to the command prompt.
Amd hence are not able to anyting to fix your machine with software.

You may need to look at ebay for a new GPU, or get hold of dell.

Sorry about bluntness didn't want to give false hope.
Reply
Reply
post #117 of 234
8/10/07 at 11:32pm
Quote:
Originally Posted by sevenflow View Post
Read through and I'm in the same boat as Ensui, almost exactly. I'll do the commands you gave him with output.txt files.
Welcome to shit creek, where paddles don't exist. :\\ I FUBAR'd mine when I DLed a German bios. I should've known better. Computer's still not fixed by the way, I haven't gotten the money to get her repaired.
Reply
Reply
post #118 of 234
8/12/07 at 9:23am
Thread Starter 
Don't let it bother you too much. I havent broken a card yet despite some rather risque flashing, but I have owned two unrecoverable cards and I know how crappy it is. I cant remember all the tricks I pulled but I managed to boot one of the broken cards only to get a non-initialization error in nvflash so it was pretty much over. Havent tried yet with the other card but I plan on using hardware mods on it.
Reply
Reply
post #119 of 234
9/16/07 at 1:06pm
what rom file do i copy into the autoexc file?.....i have a geforce go7900gs (dell e1705).... any sugestions?
Reply
Reply
post #120 of 234
9/16/07 at 1:34pm
it now beeps every time i press y is that a good or a bad thing?
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home