jzintv hackfile getting mutilated

[Swami]

Any idea what is causing my jzintv kbd/controller hackfiles to get mangled like this? They were fine on my old win10 laptop, but on my new one they keep getting ran together instead of the twin input output columns. Thanks!

[Swami]

Okay. Ugh. I tried this:

 

https://winaero.com/blog/disable-unix-line-endings-support-windows-notepad/

 

we'll see if my computer blows up.

 

Update: Nope. Files still get messed up. Tried setting both keys to 0 like on my previous laptop as well, no difference, still open messed up.

 

The problem is, I am having issues with jzintv crashing when trying to open a game, restart a game with button 0, minimize the game window from full screen, etc., since moving it to my new laptop.

 

Also, it makes it very difficult to change the settings.

[mr_me]

I use Notepad++ to edit unix style text files.

https://notepad-plus-plus.org

 

The files themselves are likely not changing. The editor might not display it properly if each line doesn't have a cr code. That website says windows notepad started to support these text files in Windows 10 Build 17661.

 

Some new computers need jzintv to be in 32-bit colour. Eg. Jzintv -z1024x768,32 romfile

Edited April 13, 2019 by mr_me

[+fdr4prez]

I agree with mr_me

 

Use Notepad++ and when it opens the file and then from the Edit menu use the EOL Conversion tool:

 

 

 

Save it, and it should be OK for Notepad, but at this point why not simply keep using Notepad++?

Edited April 14, 2019 by fdr4prez

[Swami]

I use Notepad++ to edit unix style text files.

https://notepad-plus-plus.org

 

The files themselves are likely not changing. The editor might not display it properly if each line doesn't have a cr code. That website says windows notepad started to support these text files in Windows 10 Build 17661.

 

Some new computers need jzintv to be in 32-bit colour. Eg. Jzintv -z1024x768,32 romfile

 

 

I agree with mr_me

 

Use Notepad++ and when it opens the file and then from the Edit menu use the EOL Conversion tool:

 

eol.jpg

 

 

Save it, and it should be OK for Notepad, but at this point why not simply keep using Notepad++?

 

After Notepad, I initially tried using Wordpad, which opened it with the right format, but Wordpad really screwed things up, even after switching back to Notepad as the default program for the text files, so jzintv wouldn't even open. I was worried Notepad++ might do something similar. But, after mr_me's suggestion, I tried Notepad++ and it works good for keeping the format in two columns. Then, I brought the hackfiles from my old computer over again (even the one's on the flash drive from before got mucked up by wordpad). Once, I got that down, I went through and reinstalled everything for jzintv. jzintv still crashes about half the time I try to restart a program after "game over", but doesn't seem to be crashing anymore otherwise.

 

I'm uncertain how the "-z1024x768,32" tag works if you are playing full screen. I don't know what full screen resolution jzintv is set to, but if it's the tag I use (640 x 480, 256 colors) then that is what it would be. Would that be "-z640x280, 320", or is it actually 32 at the end? Thanks.

[mr_me]

The third parameter on the -z switch is the color bit depth. Eight bit is 256 colours and 32bit is millions of colours. I have a computer where jzintv will crap out when switching to full screen or window (can't remember which). Setting the jzintv colour depth to 32-bit fixed it.

[Swami]

The third parameter on the -z switch is the color bit depth. Eight bit is 256 colours and 32bit is millions of colours. I have a computer where jzintv will crap out when switching to full screen or window (can't remember which). Setting the jzintv colour depth to 32-bit fixed it.

Okay. I'm going to see how this works out. From the observation that the restart crash only happened like 30% of the time at the time of my last post and, I think, only with homebrews, it's probably some minor Windows glitch with the software. I have not seen it the last 4or 5 times it's played, so maybe the various changed have fixed it. If not, it's very minor now. I'll update its behavior in a week or so.