Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Ultimate Thread: 4890 in Mac Pro
- Thread starter Cindori
- Start date
- Sort by reaction score
right,
took a look on your modified rom, it was bad, you had one FF to little
this should work, made from the original you posted.
http://groths.se/atiflashingtool/anothervaporx.zip
took a look on your modified rom, it was bad, you had one FF to little
this should work, made from the original you posted.
http://groths.se/atiflashingtool/anothervaporx.zip
Thanks a lot ...
... I really appreciate your efforts, guys ! Now I got a brand new ROM from Pelouche AND from Cindori, who's ever been that lucky in this thread ? Sorry I made you work both.
Cindory, once again, no offence meant, but as the natit injection method is a bit more complicated, I'm going to try what Pelouche stated in # 1666, trying the flash operation with atiWinflash in Windows (hoping that it's going to work).
I have also a suggestion to make as far as the ROM modifying scheme I tried to use (Peloche posted it at the end of # 1126) is concerned.
Instead of stating "Select octet at offset 112638 ..." maybe it would be clearer saying "Insert cursor at octet 112638 ...", because that's what made my file one FF short (if you select and paste, the selected octet disappears, while inserting the cursor conserves it). Have a look.
Thanks and bye !
... I really appreciate your efforts, guys ! Now I got a brand new ROM from Pelouche AND from Cindori, who's ever been that lucky in this thread ? Sorry I made you work both.
Cindory, once again, no offence meant, but as the natit injection method is a bit more complicated, I'm going to try what Pelouche stated in # 1666, trying the flash operation with atiWinflash in Windows (hoping that it's going to work).
I have also a suggestion to make as far as the ROM modifying scheme I tried to use (Peloche posted it at the end of # 1126) is concerned.
Instead of stating "Select octet at offset 112638 ..." maybe it would be clearer saying "Insert cursor at octet 112638 ...", because that's what made my file one FF short (if you select and paste, the selected octet disappears, while inserting the cursor conserves it). Have a look.
Thanks and bye !
Attachments
You're right bradipo concerning "Insert cursor at octet 112638", i'll update it.
But if you keep calling me "Pelouche" you'll have to call "The Rouminator"
Thanks rob, got my card flash and working. Now I might need to apply the combo 10.6.2 update on my mac because there's some quarks when I started up wow.
I'm sorry, Peloche ...
... calling you "Pelouche", that was a mixture consisting of your name and "peluche" (which means "cuddly toy" in french) (Just by the way : "bradipo" is italian and means "sloth" (the animal).)
Well, guys, here we are. Once more we have to state that, whatever precautions you may take, things can go wrong. I just tried to apply the new, foolproof ROM to my Vapor-X with atiWinflash. Want to know what happened ? Windowd freezed, and restarting it I was greeted with a black screen. The Vapor-X does not work anymore. With my old X1900XT and the Vapor-X, the MacPro can start only in protected mode of Windows (I'd heard of that, but experienced it for the first time today). It does no matter if X1900XT is put in slot 1 and Vapor-X in slot 3 or vice versa (these are physically the only possibilities, thanks to the space those two need). What a pity ! I wouldn't have done it that way if I didn't recall somebody in this thread reporting that the operation was successfull with Winflash.
I tried this because I thought maybe I could repeat my flashing operation, but atiWinflash does not lauch in this protected mode. So here we are.
Now I have to ask the question I already thought of, for pure curiosity, some day ago, only that now I have to know : do I have to reflash my Vapor-X in its original state, with all that DOS business one seems to need, or can I try to flash with Cindoris natit procedure directly over this failed attempt ?
Thanks and bye !
... calling you "Pelouche", that was a mixture consisting of your name and "peluche" (which means "cuddly toy" in french)
(Just by the way : "bradipo" is italian and means "sloth" (the animal).)Well, guys, here we are. Once more we have to state that, whatever precautions you may take, things can go wrong. I just tried to apply the new, foolproof ROM to my Vapor-X with atiWinflash. Want to know what happened ? Windowd freezed, and restarting it I was greeted with a black screen. The Vapor-X does not work anymore. With my old X1900XT and the Vapor-X, the MacPro can start only in protected mode of Windows (I'd heard of that, but experienced it for the first time today). It does no matter if X1900XT is put in slot 1 and Vapor-X in slot 3 or vice versa (these are physically the only possibilities, thanks to the space those two need). What a pity ! I wouldn't have done it that way if I didn't recall somebody in this thread reporting that the operation was successfull with Winflash.
I tried this because I thought maybe I could repeat my flashing operation, but atiWinflash does not lauch in this protected mode. So here we are.
Now I have to ask the question I already thought of, for pure curiosity, some day ago, only that now I have to know : do I have to reflash my Vapor-X in its original state, with all that DOS business one seems to need, or can I try to flash with Cindoris natit procedure directly over this failed attempt ?
Thanks and bye !
Oh, and just another problem ...
As I suspect I've to go with Cindori's atiflash to correct what happened in Windows, I tried to install the Natit. Cindori's application told me that it was successfully installed, but after ten seconds I got this message you can see below. Does this mean I'll have to create my own Natit, with Peloche's algorithm ?
As I suspect I've to go with Cindori's atiflash to correct what happened in Windows, I tried to install the Natit. Cindori's application told me that it was successfully installed, but after ten seconds I got this message you can see below. Does this mean I'll have to create my own Natit, with Peloche's algorithm ?
Attachments
Classicnotseize is a buggy printer/scanner kext. It has nothing to do with ATI Flashing Tool or Natit.
The reason it's popping up is because ATI Flashing Tool rebuilds kextcache after installing Natit, so unsupported kexts will reject like that one.
If you are not dependant on any special printer/scanner, you can remove it.
Flashing with Windows is very buggy and I do not recommend it. One should always go either DOS or OSX.
In your case OSX will not work since the firmware is broken. If Windows doesnt initialize the card, Natit won't either. Go DOS.
The reason it's popping up is because ATI Flashing Tool rebuilds kextcache after installing Natit, so unsupported kexts will reject like that one.
If you are not dependant on any special printer/scanner, you can remove it.
Flashing with Windows is very buggy and I do not recommend it. One should always go either DOS or OSX.
In your case OSX will not work since the firmware is broken. If Windows doesnt initialize the card, Natit won't either. Go DOS.
Fantastic. I don't blame anybody, of course, but this is a very frustrating situation I hoped to avoid with all these precautions ... I know simply nobody with a PC, so I can't see how to try this DOS thing.
Just to be clear : is it normal that, in case the graphic card ROM is really broken, the screen doesn't give any signal at all ? I read about screen distorsion, strange patterns, anything ... but my screen doesn't seem to know it's attached to a card. There's a screen LED that changes colour when you launch the computer, even before the graphic card sends the first gray image. With my Vapor-X, actually the computer seems to boot normally under MacOS (the hard disk noises suggest so, and it doesn't restart on its own), but the screen remains black, unaware of his being attached to the Mac. Should this be expected in the case of a broken ROM ?
Just to be clear : is it normal that, in case the graphic card ROM is really broken, the screen doesn't give any signal at all ? I read about screen distorsion, strange patterns, anything ... but my screen doesn't seem to know it's attached to a card. There's a screen LED that changes colour when you launch the computer, even before the graphic card sends the first gray image. With my Vapor-X, actually the computer seems to boot normally under MacOS (the hard disk noises suggest so, and it doesn't restart on its own), but the screen remains black, unaware of his being attached to the Mac. Should this be expected in the case of a broken ROM ?
bradipo,
If i understood very well you were supposed to wait that somebody check your rom before to flash
"Maybe somebody con control my work before I try to flash my card ?
Thanks and bye ! "
As soon as you uploaded your roms here cindori and I have posted a new EFIROM for you, was it already too late ?
Where are you leaving ? may be somebody from this forum could help you with a PC ?
If you flashed your card with a bad rom you won't get anything on your screen, did you try to disconnect your screen cable from the graphic card connector when Mac OS X is started ?
I have the same exact problem. I recently bought a Mac Pro (came last monday) and a Sapphire Vapor-X. I was able to flash the card successfully, as well as install the qe_ci package. When I restarted, my mac would continually freeze while booting up, forcing me to load the system in safe mode. Once in, I injected the card with Natit, and that solved the crashing problem.
Unfortunately, I can't get get any output from the DVI slot on the card. the VGA slot is giving me either really bad artifacting (on the login screen) or a blank screen once inside the operating system. Although, artifacting is better than "No Input Detected" I suppose. Also strange, not sure it means anything, if I plug into the VGA slot, then try to plug back into the Nvidia 9500GT that's currently in the system, I get "No Input Detected," I have to reboot in order to get a signal from the Nvidia card.
I've tried with multiple ROMs (the one animefuntv used, the two supplied to bradipo and the one supplied in the ROM pack) with no luck. I've also tried without the Nvidia card in the system. The card is working perfectly on my Windows 7 HD though.
Anyone have any idea what's going on?
Let's have fun with DOS ...
No, of course not. I took your ROM version, not mine, just half an hour after you posted it. The problem was not bad ROM (thanks to you), but the program atiWinflash that freezed my computer.
I'll try this right now. Thanks for the idea; it appeared already in this thread somewhere, but I didn't remember it.
No, of course not. I took your ROM version, not mine, just half an hour after you posted it. The problem was not bad ROM (thanks to you), but the program atiWinflash that freezed my computer.
I'll try this right now. Thanks for the idea; it appeared already in this thread somewhere, but I didn't remember it.
I'd have preferred not to be a pain in the ...
... but now that it comes to it, I have no choice.
Very well, then, let's go with this DOS. Cindori, Peloche, every time one of the thread participants asks a question about DOS, you tell it's possible to make a boot CD or a boot USB stick. Every time you refer to this other thread :
https://forums.macrumors.com/threads/238190/
What can we read there ?
Well, sorry to say so, but this description may work for whoever you like, but not for me. Just an example : this guy makes a list how to get a bootable CD beginning with "make a DOS bootable floppy or usb stick". That's not an explanation, that's pure confusion. Do I have to "make a floppy" in order to get a CD ? Floppy disks are a technology from 1980. What the heck is this supposed to mean ? I want a CD because I have no usb stick. If I had one, I'd read the list of things to do in order to get a bootable usb stick. Right ?
I suspect strongly other people suffer from the same extremely abbreviated language, too ... You noticed what AnimeFunTv did a month ago ? He asked in this very thread the DOS question, was told to look what I quoted, and the day after he bought a PC motherboard for his flashing operation, without comment. Coincidence ? Would he have had to do this if there was a chance to understand what this alien guy wrote more than two years ago ? I think not.
Look, what I'm trying to say is you, Cindory and Peloche, are already helping a lot. So please, why not trying to come up with an understandable, step by step explanation to what exactly one must do to get this d****** DOS boot CD ? If you think it is that simple, I invite you to have a look at this bootdisk.com site. There are dozens of options, versions, formats ... For heaven's sake, I never needed to burn an ISO with Nero ! First, as a Mac user since 1992, I didn't ever need to know about burning boot CDs, because if I wanted to know, I'd have bought a PC where those things are necessary ! Second, Nero is a PC program I don't own. Third, I have no ruddy idea what's the difference between a bootable CD and a normal one. WHen I burn a CD, I do it with MacOS, with a right mouse click on the folder in question. This is my level, I'm sorry. And as I said, I'm pretty sure other participants here just know to do things at this level, too, and this is why it can get so frustrating reading citations like the one of the quoted alien guy without hope to understand them if armed only with logic.
So I repeat : please, could you tell me (and others) where to go, which file (available today and not two years ago) to download, how to burn it with MacOs average resources ...
Thank you very much.
... but now that it comes to it, I have no choice.
Very well, then, let's go with this DOS. Cindori, Peloche, every time one of the thread participants asks a question about DOS, you tell it's possible to make a boot CD or a boot USB stick. Every time you refer to this other thread :
https://forums.macrumors.com/threads/238190/
What can we read there ?
Well, sorry to say so, but this description may work for whoever you like, but not for me. Just an example : this guy makes a list how to get a bootable CD beginning with "make a DOS bootable floppy or usb stick". That's not an explanation, that's pure confusion. Do I have to "make a floppy" in order to get a CD ? Floppy disks are a technology from 1980. What the heck is this supposed to mean ? I want a CD because I have no usb stick. If I had one, I'd read the list of things to do in order to get a bootable usb stick. Right ?
I suspect strongly other people suffer from the same extremely abbreviated language, too ... You noticed what AnimeFunTv did a month ago ? He asked in this very thread the DOS question, was told to look what I quoted, and the day after he bought a PC motherboard for his flashing operation, without comment. Coincidence ? Would he have had to do this if there was a chance to understand what this alien guy wrote more than two years ago ? I think not.
Look, what I'm trying to say is you, Cindory and Peloche, are already helping a lot. So please, why not trying to come up with an understandable, step by step explanation to what exactly one must do to get this d****** DOS boot CD ? If you think it is that simple, I invite you to have a look at this bootdisk.com site. There are dozens of options, versions, formats ... For heaven's sake, I never needed to burn an ISO with Nero ! First, as a Mac user since 1992, I didn't ever need to know about burning boot CDs, because if I wanted to know, I'd have bought a PC where those things are necessary ! Second, Nero is a PC program I don't own. Third, I have no ruddy idea what's the difference between a bootable CD and a normal one. WHen I burn a CD, I do it with MacOS, with a right mouse click on the folder in question. This is my level, I'm sorry. And as I said, I'm pretty sure other participants here just know to do things at this level, too, and this is why it can get so frustrating reading citations like the one of the quoted alien guy without hope to understand them if armed only with logic.
So I repeat : please, could you tell me (and others) where to go, which file (available today and not two years ago) to download, how to burn it with MacOs average resources ...
Thank you very much.
Boy I'm glad I passed on using WinFlash. I launched that twice in Win7... sometimes it would launch, other times it claimed to have missing resources. (?) Had I rushed to install my shiny new ROM I might have a brick. Okay... thankee for the DOS burning info Cindori... gonna do that this weekend.
BTW for anyone interested guy on eBay is selling the power cables for $15.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270464636969&ssPageName=STRK:MEWAX:IT
Oh, one more question... is the naming convention of the ROM important? My original ROM was named "RV790.rom" and I noticed both you and Peloche renamed the fixed ones as "EFIROMFX". Do I need to rename mine back to "RV790" before flashing or is it fine as it is? Thanks.
Name doesnt matter
I don't know Atiflash very well so I don't know how it works with different file endings (.bin, .rom, .img etc) but in ATI Flashing Tool I made a fix for that, so basiacally you can name it to "whateveryou.want" and it will still work
I don't know Atiflash very well so I don't know how it works with different file endings (.bin, .rom, .img etc) but in ATI Flashing Tool I made a fix for that, so basiacally you can name it to "whateveryou.want" and it will still work
Hi,
First, I would not try to make the dos bootable solution in OSX, I could never figure out what was needed. You have Windows in bootcamp, so lets look at that. Since I never had a floppy drive availble, I went the USB bootable route. I used the HP format tool, but I don't remember which one, so I provided the following links of some that I found:
http://h20000.www2.hp.com/bizsuppor...swItem=MTX-UNITY-I23839&jumpid=reg_R1002_USEN
or
ftp://ftp.hp.com/pub/products/servers/supportsoftware/cp006001-006500/cp006049.exe
or
http://en.kioskea.net/telecharger/telecharger-127-hp-usb-disk-storage-format-tool
(I can't remember which one)
I also needed the dos boot files, which I got from:
http://1gighost.com/ed/jamiephiladelphia/boot98se.exe
or
http://s93616405.onlinehome.us/bootdisk/win98c.zip
Use the HP tool to format the USB drive, and have it make it bootable using the above boot files. Then boot off it and use atiflash. I used version 3.75, but some indicate that version 3.6 works better.
http://www.techpowerup.com/downloads/1123/ATIFlash_3.60.html
Here are some of the atiflash commands, review them before you do anything.
http://forums.techpowerup.com/showthread.php?t=57750
K
First, I would not try to make the dos bootable solution in OSX, I could never figure out what was needed. You have Windows in bootcamp, so lets look at that. Since I never had a floppy drive availble, I went the USB bootable route. I used the HP format tool, but I don't remember which one, so I provided the following links of some that I found:
http://h20000.www2.hp.com/bizsuppor...swItem=MTX-UNITY-I23839&jumpid=reg_R1002_USEN
or
ftp://ftp.hp.com/pub/products/servers/supportsoftware/cp006001-006500/cp006049.exe
or
http://en.kioskea.net/telecharger/telecharger-127-hp-usb-disk-storage-format-tool
(I can't remember which one)
I also needed the dos boot files, which I got from:
http://1gighost.com/ed/jamiephiladelphia/boot98se.exe
or
http://s93616405.onlinehome.us/bootdisk/win98c.zip
Use the HP tool to format the USB drive, and have it make it bootable using the above boot files. Then boot off it and use atiflash. I used version 3.75, but some indicate that version 3.6 works better.
http://www.techpowerup.com/downloads/1123/ATIFlash_3.60.html
Here are some of the atiflash commands, review them before you do anything.
http://forums.techpowerup.com/showthread.php?t=57750
K
Cindori, do you have any suggestions to get my card working? Thanks,
https://forums.macrumors.com/posts/8942228/
https://forums.macrumors.com/posts/8942228/