Download Bios Folder For Ps3
Steven
Thanks again hunterk. I see that the core information says " missing, required:scph5001.bin" (PS1 US BIOS)., etc. I will get back to you once I find the correct BIOS, and try your recommendations again.
When you look under the core information tab after you have loaded the core it will tell you if it needs to be in an additional folder within your system folder as well. Some do not need to be be placed in a sub folder within your system folder. like the 5500.bin 5501.bin and 5502.bin
This was the answer I was looking for. So I put my ps1 bios into a folder and then tried to move it into the correct directory through ssh. Still no success. I continue to get the no bios error. Here is the way I moved it.
what this does is BASICALLY relocate the folder into the games sub folder but linked to the original location to nothing gets broken. it is what I did on mine and it works fine. alternatively you can reconfigure the emulator to use a separate folder for JUST the PSX bios but i figured it would be a bit of extra clutter.
Just a quickie... I have the MAME Bios files but (ideally) would like to put them in a separate folder out of the normal MAME emulator and Roms folder. I can't find a directory setting in MAME for 'bios' files and I can't see in the .ini where it could be changed?
I am running into an issue where Code Composer Studio (CCS) 3.3 isn't able to locate DSP/BIOS files when I attempt to load a project. For example, if I attempt to load the example DSP/BIOS 5.33.03 project "hello.pjt" from C:\CCStudio_v3.3\bios_5_33_03\packages\ti\bios\examples\basic\hello, I get multiple messages stating that Code Composer Studio "Cannot find file: ". Some of the files that it cannot find are buf.h62, Std.h, Sts.h, Swi.h, Tsk.h, etc. These files are all located in the bios directory at C:\CCStudio_v3.3\bios_5_33_03\packages\ti\bios\include. I also noticed that the project *.tcf file is shown in the project documents folder rather than the DSP/BIOS Config folder. I get errors when I try to build in this scenario. This has occurred with two different projects.
I am using CCS 3.3.82.13, with BIOS 5.33.03, and Code Generation Tools v6.1.20 on Windows 7 (64 bit). I understand that Windows 7 is not an officially supported operating system for CCS 3.3, but we would like to avoid upgrading at this time if at all possible. I ran all the installations and programs as an administrator. I installed Code Composer, DSP BIOS, and the code generation tools directly to the C drive (as opposed to in the Program Files folder).
I see nothing wrong with your setup. There is something wrong with the BIOS setup within CCS. It seems like you have it configured correctly in component manager but CCS is not recognizing BIOS config files and paths.
It looks like I have them both enabled (DSP/BIOS and Project Management). I didn't have a "Project Manager", just a "Project Management" option. Below is a screenshot showing the two options enabled and all the options that are disabled.
I manually re-registered projsvr.dll and bti6000.dll as you suggested. I didn't notice any change initially after re-registering the dlls and still received the same messages indicating something was wrong with the BIOS information in CCS.
However, I noticed the messages I received when opening my CCS project seemed to change when I changed the BIOS between 5.33 and 5.31. The different messages CCS displayed were the two I mentioned in my original post: "No build tools for the target specified in this project were found.." and "Cannot find file: ". One time, I changed the BIOS from 5.33 to 5.31, started CCS, and loaded the project with no messages indicating a problem. I was then able to build successfully. I then restarted CCS, loaded my project, and received one of the two kinds of messages indicating there was some problem with BIOS inside CCS.
I had been running CCS in Windows XP (Service Pack 3) compatibility mode ever since I encountered a driver problem early on (which compatibility mode didn't solve). I discovered that if I ran CCS with Compatibility mode disabled, I have been able to open and build my project successfully every time I have tried! When I re-enable Compatibility mode, I run into issues and receive CCS messages when opening my project.
It appears that my issues were solved through a combination of re-registering the DLLs and disabling Compatibility mode with CCS. I am planning on trying to install CCS on a Windows 7 PC that has never had CCS installed to verify that I can repeat all of the installation steps I used to get it working on my current PC. I should be able to determine if re-registering the DLLs is necessary to get CCS3.3 to work on Windows 7 from that.
David H said: I discovered that if I ran CCS with Compatibility mode disabled, I have been able to open and build my project successfully every time I have tried! When I re-enable Compatibility mode, I run into issues and receive CCS messages when opening my project.
this is contrary to what I have always observed. I usually recommend to run v3.3 with XP compatibility mode enabled since this works best for me. So I am surprised that turning it off works better for you. 3.3 support on Win 7 really is a crapshoot. For some, it is a breeze. Others have all sorts of problems. I'm glad that you have resolved yours.
Great question. SmartDeploy addresses BIOS updates the same way it does device drivers, with Platform Packs. Inside a Platform Pack downloaded from SmartDeploy.com you will find a BIOS folder that has the BIOS executable for the OEM. This is coupled with a preset task that queries the BIOS to get the version, then will run the update if it is needed. The great thing for customers using the packs from SmartDeploy.com is that this just happens, no need to make any modifications on your end. If you would like to add a BIOS to your own custom Platform Pack you can check out the SmartDeploy Enterprise User's Guide or the Creating Custom Platform Pack video here.
If you want to see what level the BIOS will be updated too you can check the Platform Pack. Inside the Platform Pack, under the OS node you will see a folder called BIOS. Select the BIOS node and check the right hand pane for the version that is being queried. If the version on the machine is already higher than this it will not be updated. You could also check the Deploy.log that is in C:\ Windows\Debug after a deployment completes to see if the BIOS task was executed.
Erik, is there a way to modify settings in the BIOS on deploy? For example, if a machine has both an integrated and discrete GPU, is there a way to set the option to only use the discrete GPU if the BIOS supports that option? Thanks!
Looking at what is in the BIOS folders I see a POSTIMAGE task that executes a script named DellBIOS. So I extracted the contents of the BIOS folder which contained the vb script and an exe file named OptiPlex_7760_7460_1.2.3.
Can you also reboot the computer, keep press F1 for System Information. Once it opens, please copy/paste all the information here, especially product number, motherboars info and ROM version or something similar - whatever is there...
I have already used HPSA, checked for updates and messages: The only updates it shows are: HP Universal Camera Driver 2015, Cyberlink YouCam Software SP74037 and Broadcom Wireless LAN Driver and Utility SP73093.
worked for me too, but not with the EFI\HP\BIOS\New folder. So I created all the folders that are described in the error message : EFI\HP\BIOS\Previous, Hewlett-Packard\BIOS\New, and Hewlett-Packard\BIOS\Previous. An dthen it worked. Thanks for this ! it was helpfull
I've put it on a thumb drive, I've put it on a system drive, but still get the error. When I select the option to boot from local device, I get that error as well. There have been two new BIOS releases since my current version.
In my case I had to remove encryption (bitlocker) from the D:\ drive, which stores the HP_Tools and all the folders related to the BIOS update. Once the BIOS was updated successfully, I encrypted the drive again.
b37509886e