Well the command mentioned failed, I can try setting that directly into the win3 script, but after booting with the dtv,720p setting I got the same flashing (somewhat different, but still flashes) boot up screen, then fluxbox was still pink, and now is off center about 4-5 inches to the left.
The boot text was much sharper, though, could just be the component cables in general, nothing to do with the settings I put into win3. Fluxbox itself was slightly blurred around the cursor, like a slight after image shadow, not sure if this is an intended effect or not.
If the command failed due to not thinking dtv2 was a valid configuration, what can I expect to happen by forcing it directly into the win3 script? If the configuration is still considered invalid, I mean. Or will it simply say Oh ok, its valid since it was mentioned in the win3 script?
Other then fixing this issue in fluxbox, is there a way to fix it in kloader kernal parameters so the booting text isn't flashing and making me want to stab my eyes out with a dull spork?
I have noticed certain elfs doing it, though not nearly as badly, the text itself may flash or artifact, but the whole screen doesn't flash like it does in linux. Snes Station is one of those that flash, once you launch a game the Snes station main screen will flash between frames of the game being played, but no color issues, so again, RCA will fix this, just odd that the PS2 can't use the cables all the time, only in certain situations. Games, menus, DVD movies, movies in SMS etc all work fine with them, its just linux and snes station so far.
I guess this means I need to go find someones fat PS2 with a dead laser or something for next to free (or free) and just use it for SNES station and maybe linux if I can't hammer out the settings to use the component cables properly. I'll modify the win3 script to match your settings in the morning, time is so limited with a new (first) baby (well, 4 months old on sunday) and being the only driver in the family.
Edit: Edited win3 script to say dtv2 instead of dtv,720p and I couldnt get fluxbox to even start, so dtv2 is not valid on my install for whatever reason. Trying out dtv,480p this time around. Other then that, I can only think of trying VESA and setting my own resolution settings in win3. I still don't understand how the NTSC setting breaks my component cables, its a NTSC machine on a NTSC TV.
Edit2: dtv,480p boots, is slightly larger then my screen area, and its still pink! argh.
Edit3: VESA settings are black screen in fluxbox, I'm getting annoyed now.
Edit4: Changed the kloader config to crtmode=dtv,480p this has stopped the flashing, but text is still pink, win3 script was reset to the previously workable dtv,480p as well. Next I'll try setting kloader config to crtmode=dtv2 and seeing how that goes, if text goes normal we're on the right track and its something outside of kloader and its kernal/fluxbox related. Side note, kloader won't let me use my usb keyboard to edit the strings, I have to edit it on my pc then reload it from usb, anyone else get this?
Edit5: set dtv2 in kloader kernal strings, text is still pinkish, however much smaller then before, very hard to read, next step is to specify it in win3 since the kernal doesn't discard it from kloader.
Edit6: Once again dtv2 in win3=failsauce, refuses to run with that switch in there. kloader will use it, so I'm missing something when it comes to fluxbox using it. I'm now out of ideas, so my current setup for video is:
What if I don't put a resolution mode after dtv, will it default to something? Since my HDTV is 720P I'm not sure what it will do with an interlace signal if it defaults to one.