Main > Software Forum

NullDC (New Dreamcast Emu)

<< < (5/6) > >>

jcrouse:

--- Quote from: Howard_Casto on April 30, 2007, 10:41:36 pm ---You must have an odd setting in nulldc somewhere because my images are in the same format and it doesn't do that.  Perhaps you've changed from the default cdrom plugin?

--- End quote ---

I agree from a troubleshooting stand point that it seems that way. However, this is happening on two seperate systems. I also whacked everything on both systems and started from scratch and still get the same results with the default install settings. It's not a big deal. I'll wait for the next release and see what has been added/changed. I don't expect you to help fix the problem I just wanted to get it documented somewhere in case someone else is having similar issues.

John

Howard_Casto:
Well I understand that, but since the problem seems to be only happening to you and it's happening on two seperate systems (thus eliminating a hardware/os issue) it's likely user error unfortunately and we should be able to figure it out....  Also it's unlikely that future versions will fix the issue if it's exclusive to you. 

Let's see, what I can think of...

Are your dc images bootable?  Some trickery has to be done to make dc images work.  Basically if they booted in chankast they'll boot in nulldc. 

You need to set a full path.... relative paths don't seem to work. 

My script turns OFF default booting after it completes as it's annoying when using the program manually.  That isn't your issue, but just keep that in mind. 

The default image is not loaded when you start up nulldc, but when you select "normal boot" or high level booting.  That should be obvious, but you know, just in case. 

Image reader plugin is what I am using.... I don't think the other one even works right.  Not sure if that's the default or not (sorry I didn't notice that before). 

The only way I can replicate your problem is if I set to an invalid path, so i'd suggest checking that for typos. 

I hope that helps.

jcrouse:

--- Quote from: Howard_Casto on May 01, 2007, 01:29:11 pm ---Well I understand that, but since the problem seems to be only happening to you and it's happening on two seperate systems (thus eliminating a hardware/os issue) it's likely user error unfortunately and we should be able to figure it out....  Also it's unlikely that future versions will fix the issue if it's exclusive to you. 

Let's see, what I can think of...

Are your dc images bootable?  Some trickery has to be done to make dc images work.  Basically if they booted in chankast they'll boot in nulldc. 

You need to set a full path.... relative paths don't seem to work. 

My script turns OFF default booting after it completes as it's annoying when using the program manually.  That isn't your issue, but just keep that in mind. 

The default image is not loaded when you start up nulldc, but when you select "normal boot" or high level booting.  That should be obvious, but you know, just in case. 

Image reader plugin is what I am using.... I don't think the other one even works right.  Not sure if that's the default or not (sorry I didn't notice that before). 

The only way I can replicate your problem is if I set to an invalid path, so i'd suggest checking that for typos. 

I hope that helps.



--- End quote ---

Bootable = yes. They are all bootable and actually tested in a real DC. Also, they play fine going through the nullDC menuing system to load and start the game.

Full path - Even if I go into the cfg file that you modify, set the first parameter to "1" and the second parameter to the image It doesn't load. When I select start it still pops up the open file dialog box. As stated earlier, the file type filter is "mds" but the file box displays mdf files. There are definately minor issues with the code.

You're wrapper has nothing to do with my problems. Even nullDC on it's own deosn't work for me using the default Image Reader plugin. Yes it is the default, FYI. Please see the previous post for a description of what happens.

The other plugin, ZnullGD, seems to work good for me if I first mount the image in Daemon Tools, again just an FYI. I even modified your script to work with this plug in and it works great, basically just sends the start command, from the command prompt but this is where I have the MameWAH focus issue.

There shouldn't be any typos. I even created an image with no spaces in the file name, just for testing.

Thanks,
John

Howard_Casto:
Yeah I read it believe it or not and I know it's a glitch in nulldc, but I've still managed to get my mds files working.  I did find one that is doing what you described since then though, so it might have something to do with how the image is authored.  Cdi and img files have the same basic structure, so your easiest solution might be to just convert them (which is what I am doing.)

jcrouse:
LOL, I already tried that.

John

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version