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

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.

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)
It would be less sloppy to call another batch file to do the flashing but ah, I'll keep it simple.

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.

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

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.

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' ....

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

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

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.

I did that, it didn't work. I am, as you so eloquently put it, buggered.

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.

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.

what rom file do i copy into the autoexc file?.....i have a geforce go7900gs (dell e1705).... any sugestions?

it now beeps every time i press y is that a good or a bad thing?