Difference between PMT1 and PMT3

[cleatus12r]

Yeah. That's it.

What you need to do is delete the first 57344 bytes. Use the "edit" and "select block". Then with the selector in "dec", type in 57344 and hit "ok". Delete that block. You should start with a hex value of "27FE".

Select another block of 32768 bytes and copy that to a new hex editing window.

There's your emulation binary!


When you go back in after changing, use the original 224K binary and insert the modified 32768 bytes into the 224K program.

[907DAVE]

Ok....so bear with me here.

So after selecting and deleting 57344 bytes I am left with this.......








And after selecting a block of 32768 bytes and coping into a new window.........












Then I will save this, and that's my emulator binary?





How does someone learn this stuff? The more I ask about the more I realize how very little I think I know.

[cleatus12r]

'zactly right.

It starts out as a pretty tedious process but after you do it a few dozen times........

You wouldn't believe how many times I compared different files and used a hex editor to get the desired results. As long as you know how to do it now, that's all there really is to it.

Just be glad Bill doesn't encrypt his binary...we'd be up the proverbial creek without a paddle. I worked with Sniper stuff for about a year before I bought Bill's version. Sniper's encryption setup is a crock. You can't run a Romulator with it anyway.

[907DAVE]

Originally Posted by cleatus12r

You wouldn't believe how many times I compared different files and used a hex editor to get the desired results.

So now I am curious, can you explain this?

[cleatus12r]

I have sat in front of this computer staring at binary for longer than I care to recall back when I first started getting into this about 2 years ago. I got some stuff to read PCM memory, got some more stuff to try to disassemble the code, got a lot more stuff to actually graph out the binary values.....to no real success.

Now I use a hex editor a lot just to make different size files (for different types of chips) and for emulation. I usually rehash my tune list about once a week when I pick up something different that works better so I always have to go back and make new 32K/224K/256K binary. It's a viscious cycle.

Anyway, that's boring.

[907DAVE]

Originally Posted by cleatus12r

'
Anyway, that's boring.

Hardly! I think that is some pretty cool stuff, just wish I had a better understanding of all this fancy computer stuff.

I need to find a "Computer's For Dummy's" book...........

[907DAVE]

Originally Posted by cleatus12r

I have sat in front of this computer staring at binary for longer than I care to recall back when I first started getting into this about 2 years ago. I got some stuff to read PCM memory, got some more stuff to try to disassemble the code, got a lot more stuff to actually graph out the binary values.....to no real success.

What were you expecting to find?

I am confused about the thought process behind this, why not use Minotaur to do the same thing?

[cleatus12r]

Well my original thinking was that "I can do this myself. No need to pay for something I can figure out."

Well, it turns out that I couldn't do it.....not within the next 5 years or so anyway.....so being a guy and needing everything "right now", I finally did end up buying some stuff (Sniper Delta Force) after trying to get ahold of Bill for his. Unfortunately, PHP was having the same email problems that they are still having and none of my correspondence went through so I ended up with Delta Farce.

However, knowing what I know now about the binary structuring and addressing, there is no possible way that I would have been able to figure out any of my own definitions because I would have had no clue as to how much stuff I actually would have needed to find to get where I am now.

Minotaur wasn't available to the public when I started and unfortunately I have ended up spending an extra $6,000 on something I can't use except for the chip burning function....so I have a $6K chip burning application now that is really inconvenient to use. Phoenix Flash doesn't work with the chips that are coded for my Sniper vendor (David Lott) so I have to make a calibration in Minotaur, save it, open it in Delta Force, save it, THEN finally burn it to the chip. It's a real PITA and one of these days I'll just buy a burner from Bill and start using his coded chips. It's really inconvenient to have duplicates of EVERY flippin' program on this computer.

[907DAVE]

Originally Posted by cleatus12r

When you go back in after changing, use the original 224K binary and insert the modified 32768 bytes into the 224K program.

So.......... After I am finished with the file (32k), how do I get it back into the original program?

Do I first select the 57344 bytes, cut them out of there and set them aside (new window). Then select the next block of 32768, delete them, and paste in my modified file, and then paste the first 57344 bytes back in?

Thanks

*Edit* That does not work.

[907DAVE]

Here is what I did, set the offset at 57344, then replaced the next 32768 with the modified set. Seemed to work.

Not sure why my first attempt(s) failed......

On a side note the Hex Editor Neo program does not seem to get along well with Minotaur.......can only use one at a time.

Stupid computers.