Psx Bios Files

0 views

Skip to first unread message

Piren Cobrin

unread,

Aug 3, 2024, 4:28:14 PM8/3/24

to blaserpona

Welcome to cdromance BIOS section. Over here, we have a great selection of console BIOS files to use on emulators like the Dreamcast Bios for Redream/Reicast on Android devices, SEGA CD Bios for RetroArch, RetroPie, PicoDrive and many more. These BIOS can be used in any device, PC's, phones, tablets, RP (Raspberry Pi), so look no further you have found the best BIOS collection on the internet!

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.

All is working perfectly fine...except I have no idea where to but the BIOS files and how to configure LaunchBox / MAME with them. I have searched but was somewhat overwhelmed with the results and could do with some help - and as simple as possible please!

Mame bios files can get dumped into the same folder as Mame roms. If you choose to put them elsewhere you just need to point Mame to that folder location. Launchbox only needs to know where the roms are. Unless you used the full Mame romset import option then it does not care as long as you have a full romset and Mame is already pointing to it.

Ah, I see. I think I understand! I downloaded the full .213 ROM set from a certain members only site. I was under the impression that some games needed a BIOS ROM; I'm yet to encounter a game that doesn't work yet so I'm probably okay. Thanks for replying!

Some games do need bios files but if you have the full MAME ROM set the bios files that are also in the MAME bios packs are already included in them so there is no need to download them or add them to your ROMs folder as they should already be present.

How do I tell Mame where to look for the Bios files? The Bios files I have are named exactly the same as the Mame roms, so it tries to overwrite. I created a new folder called bios, but I'm not exactly sure how to tell Mame where to look.

OMG. I'm so stupid. I didn't realize the Rom folder already had the damn bios files! I checked it more thoroughly and I see that the bios files are already in there. That's why it's asking to overwrite.

I wish to flash the bios on a hp envy 15 1170ez. The current insyde bios version is f2.b

I am trying to get the bios file for this laptop but everything that I find leads to a softpaq setup program that only runs on windows.

The 'DOS based flash files' that means the executable files for the setup program like insydeflash.exe or the .bin files that are to be placed on the disk?

Where could I find those bin files?

I could already extract the file from the hp ftp server once but only got another executable (a file starting the InsydeFlash settings program). Extracting this second executable did not result into any files.

.
Using 7zip instead of using AZarc resulted in a bunch of files that I did not see before. In my case there are two .fd files among them, I hope they can help me further. Probably some settings with the AZarc extraction program or maybe it is not able recognize the type of compression.

How would I identify what variant(s) of a black Pro 6 I have? And having done that, where can I get the newest bios that allows for use of drives larger than 4TB?

I have two, one is an early Pro Pioneer, and the second was bought used, already updated to 6.10.x.

I remember seeing in the forum that there were some very early Pro6 models that are a bit different and can't have the BIOS updated to accept a faster processor. But the BIOS update will simply fail on them, not brick it. But AFAIK, anything with FLAME6-MB V1.6 can be updated to 2.0. There have been posts on how to do the update if you've already converted to OS6, but they are old. Personally, I recommend using a spare drive to downgrade back to 4.2.31, then installing the BIOS update, then re-converting to OS6 with that spare drive.

This afternoon while not particularly using my computer, I was stunned when suddenly ESET popped up and gave me two extremely worrying warnings about viruses being detected on my system. I was not trying to access the files at the time, and these files have been on my computer for nearly a year (since 2015). They correspond to a BIOS update package that I required for my Nvidia GTX 980 Ti graphics card long, long ago.

I'm very concerned that this may indicate a deeper system infection spilling over into or corrupting/infecting older files. But the fact that both the hashes discovered and cleaned by ESET return 0 detections on VT seem to indicate that these may not actually be risks? I'm confused, and afraid.

3) These files were part of a backup of BIOS files I needed for my old GPU. Why would they be seen as malicious? Could they be infected, and if so, why would the infected files have the same hash as files seen previously by VT? Notably, first seen by VT in 2011?

It's just mad about the BIOS/driver whatever this is , because it's vulnerable , you can exclude the detection so ESET can be quiet about it , or just update the BIOS/drivers(more recommended) which will fix the vulnerability and make ESET go quiet.