|
|
|
|||||||
| About Us | Register | FAQ | Members List | Calendar | Mark Forums Read |
 |
|
|
LinkBack | Thread Tools | Display Modes |
January 1st, 2005
|
#21 (permalink) |
|
Registered User
Join Date: Oct 2004
Location: Michigan, USA
Posts: 33
|
More CVS BIOS Feedback
Here is a little more user feedback on the bios issue. I am doing a standard install of 1.0.7 and then changing the “usejaguarbios = 0” to 1 in the cfg file. Here is the pertinent section log file.
DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Successfully initialized. CDINTF: Found CD-ROM device [SONY CD-ROM CDU5221]. HAID:0, TID:0 LUN:0 CDINTF: Found CD-ROM device [TDK DVDRW1280B]. HAID:1, TID:0 LUN:0 CDINTF: Found CD-ROM device [Generic DVD-ROM]. HAID:5, TID:0 LUN:0 About to attempt to load BIOSes... VJ: Loading "./bios/jagboot.rom"...OK (131072 bytes) VJ: BIOS is available... VJ: Loading "./bios/jagcddev.bin"...Failed! VJ: CD BIOS is not available... Initializing video subsystem... Initializing GUI subsystem... I then modify the cfg file like this (comment out the default CDRom Bios and point to my own: JagBootROM = ./bios/jagboot.rom CDBootROM = ./bios/jagcd.rom #CDBootROM = ./bios/jagcddev.bin EEPROMs = ./eeproms ROMs = ./ROMs Here is the log file: Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Successfully initialized. CDINTF: Found CD-ROM device [SONY CD-ROM CDU5221]. HAID:0, TID:0 LUN:0 CDINTF: Found CD-ROM device [TDK DVDRW1280B]. HAID:1, TID:0 LUN:0 CDINTF: Found CD-ROM device [Generic DVD-ROM]. HAID:5, TID:0 LUN:0 About to attempt to load BIOSes... VJ: Loading "./bios/jagboot.rom"...OK (131072 bytes) VJ: BIOS is available... VJ: Loading "./bios/jagcd.rom"...OK (262144 bytes) VJ: CD BIOS is available... Initializing video subsystem... Initializing GUI subsystem... About to start GUI... GUI: Inside GUIMain... GUI: Resetting Jaguar. So far so good (I think). I then replace the executable with the CVS exe and get this: DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Successfully initialized. CDINTF: Found CD-ROM device [SONY CD-ROM CDU5221]. HAID:0, TID:0 LUN:0 CDINTF: Found CD-ROM device [TDK DVDRW1280B]. HAID:1, TID:0 LUN:0 CDINTF: Found CD-ROM device [Generic DVD-ROM]. HAID:5, TID:0 LUN:0 About to attempt to load BIOSes... VJ: BIOS is not available... VJ: CD BIOS is not available... Initializing video subsystem... Initializing GUI subsystem... About to start GUI... GUI: Inside GUIMain... GUI: Resetting Jaguar. This happens no matter which method from above I use to try and point to a CD Bios. It must be something in the CVS builds attempt to path to the bioses. Enjoy, John |
|
|
|
January 1st, 2005
|
#22 (permalink) |
|
Emu author
 Join Date: Jul 2003
Posts: 130
|
Thanks for the info. Stuff like this is useful, as it helps to pinpoint problems.
 I just made another fresh build which should give more info into the problem. Download it from http://icculus.org/virtualjaguar/vj.exe and post the relevant parts of the log file.  One thing to keep in mind is that this code is the new time-based code and as such only responds to the ESC key when running a ROM. 
Last edited by Shamus; January 2nd, 2005 at 00:03. Reason: Missing info |
|
|
|
|
January 2nd, 2005
|
#23 (permalink) | |
|
Registered User
Join Date: Oct 2004
Location: Michigan, USA
Posts: 33
|
Quote:
Test #1 Cfg File: # Jaguar BIOS options: 1 - use, 0 - don't use useJaguarBIOS = 1 # Jaguar ROM paths JagBootROM = ./bios/jagboot.rom #CDBootROM = ./bios/jagcd.rom CDBootROM = ./bios/jagcddev.bin EEPROMs = ./eeproms ROMs = ./ROMs Log File: DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Successfully initialized. CDINTF: SCSI command 12 failed [Error: 00]. CDINTF: SCSI command 12 failed [Error: 00]. CDINTF: Found CD-ROM device [Generic DVD-ROM]. HAID:1, TID:0 LUN:0 About to attempt to load BIOSes... JaguarLoadROM: Attempting to load file './bios/jagboot.rom'...Succeeded in finding extension (.rom)! VJ: Loading "./bios/jagboot.rom"...OK (131072 bytes) VJ: BIOS is available... JaguarLoadROM: Attempting to load file './bios/jagcddev.bin'...Succeeded in finding extension (.bin)! VJ: Loading "./bios/jagcddev.bin"...Failed! VJ: CD BIOS is not available... Initializing video subsystem... Initializing GUI subsystem... About to start GUI... GUI: Inside GUIMain... GUI: Resetting Jaguar... Summary: With this setup everything launched correctly. However, on a side note, there was NO sound. Test #2 Cfg File: # Jaguar BIOS options: 1 - use, 0 - don't use useJaguarBIOS = 1 # Jaguar ROM paths JagBootROM = ./bios/jagboot.rom CDBootROM = ./bios/jagcd.rom #CDBootROM = ./bios/jagcddev.bin EEPROMs = ./eeproms ROMs = ./ROMs Log File: DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Successfully initialized. CDINTF: SCSI command 12 failed [Error: 00]. CDINTF: SCSI command 12 failed [Error: 00]. CDINTF: Found CD-ROM device [Generic DVD-ROM]. HAID:1, TID:0 LUN:0 About to attempt to load BIOSes... JaguarLoadROM: Attempting to load file './bios/jagboot.rom'...Succeeded in finding extension (.rom)! VJ: Loading "./bios/jagboot.rom"...OK (131072 bytes) VJ: BIOS is available... JaguarLoadROM: Attempting to load file './bios/jagcd.rom'...Succeeded in finding extension (.rom)! VJ: Loading "./bios/jagcd.rom"...OK (262144 bytes) VJ: CD BIOS is available... Initializing video subsystem... Initializing GUI subsystem... About to start GUI... GUI: Inside GUIMain... GUI: Resetting Jaguar... Summary: No sound here either. I am figuring you daisbled the sound for testing of some sorts. I do have a question. You can see in the first test I use the default settings for the CD Bios. Is this built into the code, because I don't have and can't find a file by that name? Also, during furter testing should I try it both ways or just with the default setting using the previously mentioned bios? Also noted was that the green tesxt that displays briefly about CRC or something (I forget) didn't appear at all with the new exe. Again, I figure that this is something that you disabled in the code. If I can help in any other way with testing just post back to this thread. John |
|
|
|
|
|
January 2nd, 2005
|
#24 (permalink) |
|
Emu author
Join Date: Jul 2003
Posts: 130
|
This is what I thought would happen.
My guess is the CVS Compile guys forgot to "compile clean all" when building the latest CVS--not all header dependencies are fully fleshed out, so it's possible some of the .o files were stale in their build.How 'bout it XTale? The kinds of problems John is describing with your builds shouldn't be happening (i.e., not finding the BIOS even though the paths are correct)... :P |
|
|
|
|
January 2nd, 2005
|
#25 (permalink) |
|
AEP-Emu.de staff
Join Date: Oct 2002
Location: germany
Posts: 30
|
hm...
that could be possible. I don't remeber if I did a compile clean before.. time was very limited I'm currently not on my own pc, I'll have a look as soon as I get back home (to my own computer). Sorry for the problems - but shouldn't a new build even work without doing a make clean? |
|
|
|
|
January 4th, 2005
|
#28 (permalink) | |
|
Registered User
Join Date: Oct 2004
Location: Michigan, USA
Posts: 33
|
Quote:
DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK CDINTF: Could not load WNASPI32.DLL! CDINTF: Failed to init Win32 ASPI layer! About to attempt to load BIOSes... VJ: Loading "./bios/jagboot.rom"...OK (131072 bytes) VJ: BIOS is available... VJ: Loading "./bios/jagcddev.bin"...Failed! VJ: CD BIOS is not available... Initializing video subsystem... Initializing GUI subsystem... About to start GUI... GUI: Inside GUIMain... GUI: Resetting Jaguar... --> GPU stats were reset! Jaguar: 68K reset. PC=E00008 SP=00000000 GUI: Clearing BG save... VJ: Loading "c:\vj\roms\test.j64"...OK (4194304 bytes) CRC: E28756DE EEPROM: Could not open file "./eeproms/E28756DE.eep"! GUI: Bypassing GUI since ROM passed in on command line... --> GPU stats were reset! The build appeared to be fully intact with sound and working controls. John |
|
|
|
|
|
August 11th, 2005
|
#30 (permalink) |
|
Emu author
Join Date: Jul 2003
Posts: 130
|
Wow, time flies when you have babies.
Anyway, I thought I'd post another progress report here in the meantime. The next release is a big enough change from the previous version to warrant a minor version bump, so it should be 1.1.0. The new timer system seems to be fairly stable and the new blitter is coming along nicely. A lot of bugs that were seemingly unfixable have been squashed with the new blitter core. That and some bad assumptions in the memory mapped portion of the blitter have been corrected as well. I'm hoping to post some new screenshots soon to showcase the improvements.
|
|
|
|
|
October 9th, 2005
|
#31 (permalink) |
|
AEP-Emu.de staff
Join Date: Oct 2002
Location: germany
Posts: 30
|
I tried to create a new 1.1.0 build and postet it to my page at http://cvscompile.aep-emu.de/vjaguar.htm
But I'm not sure if it works - SDL crashes on my laptop, but that maybe the fault of that stupid IntelShared Card. Maybe someone else could give it a try. |
|
|
|
|
January 19th, 2006
|
#35 (permalink) |
|
Emu author
Join Date: Jul 2003
Posts: 130
|
Time flies, etc... :P My son is 14 months old now--damn, time really DOES fiy!
Just thought I'd post a quick note to say that I'm not dead and neither is VJ. The new blitter is almost 100% accurate (I'll explain why once it's done ), there's just a small, annoying, off-by-one bug that's holding things up at this point. The new blitter is unoptimized, though, so VJ will be a bit slower overall. The good news is that since it will be correct, we can then go back a speed it up.
|
|
|
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
