forums.marpirc.net

Looks like it's out...
http://www.mame.net/downmain.html

Please do all take note that this version will now create an nvram (as well as cfg, diff, and whatever else) folder for you. Isn't that helpful?

...is there anything we can do about that Barry? To prevent mame from doing that I mean?

How about creating a read only dummy file called 'nvram' and putting it in the MAME directory, would that work?

whatsnew.txt says it only applies to the win32 version... FUCK YEAH, DOS FOR LIFE BITCHEZZZZ!

(never mind the fact that there is no DOS binary up yet on mame.net) :(

I agree with bbh : DOS !!
And I hope it is possible to have an alphamame63 DOS for t6 ... is it ?

a very good solution LORDGAZ but i did it with each *.nv but your method is the best (directly make read-only a text file named nvram)

Thanks Borjaquake. Let me clarify the method though, I typed that post very quickly last thing at night.

To prevent the nvram folder from recreating itself:

1. DELETE the nvram folder.
2. Open up notepad and save an empty text file inside the MAME directory.
3. Rename this file to 'nvram' without any extension, ie no .txt in the filename.

Now MAME can't create a new nvram folder because a file exists with the same name. Btw there's no need to change the read only attribute.

Thanks Gary! It works great!

QRS

Maybe Im crazy

But don't the file types have to be the same in order for this to work. Creating a text file called nvram doesn't stop you(or Mame for that matter) from creating a folder called nvram in the same directory. Ive been trying to delete the nvram file in mame32 .63 and haven't had any luck yet. Now if I were to create a FOLDER called nvram. Mame wouldn't be able to overwrite it because you can't have two folders with the same name. However in this instance mame just uses the newly created nvram folder as the one it would have created. Just need a little more guidance. Thanks

I bet you have Windows set to not show file extensions. Enable the display of file extensions, and rename the file to 'nvram', not nvram.txt.

COPY CON NVRAM at a command prompt should work too.

mahlemiut wrote:I bet you have Windows set to not show file extensions. Enable the display of file extensions, and rename the file to 'nvram', not nvram.txt.

COPY CON NVRAM at a command prompt should work too.

COPY NUL NVRAM would work much better. Since you don't have to do anything else after typing the command (I forget offhand how to end the copy con thing, for it to actually write to the file).

Ahhhhh!!!!

I knew it was right under my nose. Mucho thanks Guys!!