07-06-2017, 12:00 AM
wulf... first you thought it was the hdd, then you think its the bios. Allow me to drop a bit of knowledge on you.
Your Hdd is detected by the bios. That part is on the control board that is on your hdd.. it tells the bios how big your drive is, how many cylinders and heads, etc. all of the technical details. If your bios isn't seeing the disk, its either the control board on the disk that has gone bad OR the bios. It is much more likely its the disk. It happens. That is why manufactures publish "mean time between failures", aka the average time you can expect it to live. Some disks will make it that long, others wont.
Your bios on the other hand is an extremely complicated piece of software. There are protections upon protections to stop software from writing to it. Even when it is writeable from windows, it requires a special program FROM THE MANUFACTURER to be able to do so. This isnt an open standard, and how they interface with the bios is pretty well guarded. The bios is also VERY small. They dont leave much room in the flash memory for the bios to be edited.. it would have to be done in binary or hex. Any unauthorized edits would cause your system to throw an error about the CRC being wrong. That is a cyclical redundancy check.. a self check to make sure the bios hasn't been tampered with. Because the bios is written for that exact set of hardware, its very very very specialized code. Very few people are actually able to understand it well enough to modify it. Any error in the code will most likely result in a computer that doesnt boot. It wont even attempt to boot. It will fail to even show the splash screen or check the ram or anything.. Nothing but a black screen.
For pcsx2 to attempt to write to your bios, it would have to know
1. what bios you have, which means which mfg your computer is, the hardware specs, etc. That is retrievable
2. HOW to access the bios - nope, not gonna happen. Read things its reporting to the os like ram.. yes. Access the physical bios it self in a read/write state.. I'll learn to fly first.
3. Not only how to access it, but how to write to it - yeah, again.. I'll fly first
4. Then it would have to contain code for every single bios type out there for every single manufacturer of motherboards (thousands wouldn't be out of the question), be able to identify it, write to it, and not brick most of them (even though the bios is small per machine, that many iterations and minute changes would be a HUGE code base).. how big is this download again?
5. Youre ps2 bios is just like your computer bios, and just as unique. Its code is 100% incompatible with desktop computers though, and attempting to slip any of that in would literally turn your computer into a boat anchor.. no display at all... besides, it probably wont fit into the flash rom.
6. Programs you load dont interact with the bios in a read write state unless its from the motherboard manufacturer. Your os can read it, but not modify it... Any program that needs information about your computer gets it from the operating system, not the bios,.. which can only read your bios (and the controller board on your hard drive.. that is called firmware, but is essentially the same thing as the bios for the hdd).
In short, it is NOT possible to even attempt to modify your bios from pcsx2, the ps2 bios you load is read by the program, not inserted anywhere. It also didnt make your hdd disappear from your bios, because it would require the ability to write to the bios to do that. It didnt damage the control board on your hdd.
Blaming pcsx2, on your computer dying is about as logical as blaming your new tv for killing your vcr.
Your Hdd is detected by the bios. That part is on the control board that is on your hdd.. it tells the bios how big your drive is, how many cylinders and heads, etc. all of the technical details. If your bios isn't seeing the disk, its either the control board on the disk that has gone bad OR the bios. It is much more likely its the disk. It happens. That is why manufactures publish "mean time between failures", aka the average time you can expect it to live. Some disks will make it that long, others wont.
Your bios on the other hand is an extremely complicated piece of software. There are protections upon protections to stop software from writing to it. Even when it is writeable from windows, it requires a special program FROM THE MANUFACTURER to be able to do so. This isnt an open standard, and how they interface with the bios is pretty well guarded. The bios is also VERY small. They dont leave much room in the flash memory for the bios to be edited.. it would have to be done in binary or hex. Any unauthorized edits would cause your system to throw an error about the CRC being wrong. That is a cyclical redundancy check.. a self check to make sure the bios hasn't been tampered with. Because the bios is written for that exact set of hardware, its very very very specialized code. Very few people are actually able to understand it well enough to modify it. Any error in the code will most likely result in a computer that doesnt boot. It wont even attempt to boot. It will fail to even show the splash screen or check the ram or anything.. Nothing but a black screen.
For pcsx2 to attempt to write to your bios, it would have to know
1. what bios you have, which means which mfg your computer is, the hardware specs, etc. That is retrievable
2. HOW to access the bios - nope, not gonna happen. Read things its reporting to the os like ram.. yes. Access the physical bios it self in a read/write state.. I'll learn to fly first.
3. Not only how to access it, but how to write to it - yeah, again.. I'll fly first
4. Then it would have to contain code for every single bios type out there for every single manufacturer of motherboards (thousands wouldn't be out of the question), be able to identify it, write to it, and not brick most of them (even though the bios is small per machine, that many iterations and minute changes would be a HUGE code base).. how big is this download again?
5. Youre ps2 bios is just like your computer bios, and just as unique. Its code is 100% incompatible with desktop computers though, and attempting to slip any of that in would literally turn your computer into a boat anchor.. no display at all... besides, it probably wont fit into the flash rom.
6. Programs you load dont interact with the bios in a read write state unless its from the motherboard manufacturer. Your os can read it, but not modify it... Any program that needs information about your computer gets it from the operating system, not the bios,.. which can only read your bios (and the controller board on your hard drive.. that is called firmware, but is essentially the same thing as the bios for the hdd).
In short, it is NOT possible to even attempt to modify your bios from pcsx2, the ps2 bios you load is read by the program, not inserted anywhere. It also didnt make your hdd disappear from your bios, because it would require the ability to write to the bios to do that. It didnt damage the control board on your hdd.
Blaming pcsx2, on your computer dying is about as logical as blaming your new tv for killing your vcr.
amd tr 1950x amd ryzen 5 2500u
asrock x399 taichi amd vega 8
XFX Radeon rx570 16gb ddr 4 2400 ram
32gb gskill ddr4-3200 1tb nvme ssd
Debian Bullseye 480gb sata ssd
Custom loop water cooled HP envy x360
nzxt 340 case
asrock x399 taichi amd vega 8
XFX Radeon rx570 16gb ddr 4 2400 ram
32gb gskill ddr4-3200 1tb nvme ssd
Debian Bullseye 480gb sata ssd
Custom loop water cooled HP envy x360
nzxt 340 case
![[Image: giphy.gif]](https://media.giphy.com/media/K6VhXtbgCXqQU/giphy.gif)
. But hey, points for trying to explain it anyway
