> Stephen> In my experience: zero. In four years of constant use, I have > Stephen> not had a single program which only worked by disabling JD -- > Stephen> game, demo, or otherwise. I have had programs fail with the > > OK. Sounds like I won't bother and just go on using it with JD perma- > nently installed. If I really need the original ROMs I always have the > original, and, um two more 64s :) > Actually I'm amazed that JD works with my FC3 cartridge. They even > cooperate -- FC3 hogs the F-keys (and I think I prefer that) but all > the JD @-commands still work. No big loss -- the JD function keys are really lame :). I use it with AR often enough (I like the AR monitor). AR intercepts @ directives and such, but I can still send JD commands to the drives by using a quote (i.e. @"CD:BLAH instead of @CD:BLAH, which gets very confusing after a while ;). Speaking of AR, I've actually got a program (which I wrote) which fails with AR fastload enabled, even though it only uses the jump table. Pretty weird (not to mention annoying). Anyways, I'm sure you'll be gushing over JD in no time along with the rest of us who are 'in the know' :). > Well, at least I managed to find the problem -- CMD managed to burn > JiffyDOS in the lower half and the Basic ROM in the upper half. Small Oops :) -Steve - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail cbm-hackers-request@dot.tcm.hut.fi.
Archive generated by hypermail 2.1.1.