Jump to content

Faicuai

Members
  • Content Count

    1,961
  • Joined

  • Last visited

Community Reputation

1,304 Excellent

3 Followers

About Faicuai

  • Rank
    Stargunner
  • Birthday October 11

Profile Information

  • Gender
    Male
  • Location
    Florida, U.S.A.
  • Interests
    Auto Performance, Photography, Retro-Computing, Audio/Video, HOT girls!

Recent Profile Visitors

13,280 profile views
  1. Looks much better than anything I ever imagined! TIX article is REALLy nice (!) Congrats to all! Bring it on!
  2. This is PERFECT. It effectively addresses the "phantom" drop of .ATRs attached in XL/XE modes, before transitioning into a Colleen profile, and then back out again to XL/XE profiles. Best part: it does not seem to matter what you do in the Colleen profile slot (e.g. changing to XL/XE and back to Collen, without ever leaving the profile slot). .ATRs don't seem to go orphan and "slaughtered"... THANKS!
  3. My apologies for responding late but... I have been immersed on other issues, but also testing as much as I could... User-interface issues seem fully corrected. I would only recommend consider not dropping (instead) .ATRs during a [ XL-> Colleen -> XL ] profile navigation sequence... (said in other words, make the Colleen profile separate / abstract from whatever happens on XL/XE ones, which by nature is, as there is no PBI-rom accessible on Colleen OS loads). The reasons for this is that I often start on XL/XE mode, with .ATR images attached, then temporarily switch to Colleen, test something there, then come back to XL/XE mode, still needing the .ATRs I had attached. If they are dropped, I then have to go back Loader menu, re-attach, and resume work. However, if the above is not possible or, for some reason, not consistent with other operating principles already part of the BIOS logic, then let's move fwd. as it is, now. A big THANKS for such a lightning-fast fix, though!
  4. A little corner... where the seemingly impossible happens...
  5. This is beautiful! Isn't this what we need to run a 200-400 Mhz 6502-compatible CPU board with its one memory space, and stream, at local-bus speed, pre-cooked GFX-data to be displayed immediately by ANTIC and GTIA? Does the local 6502 remains active with EXSELin use? The idea is to let the high-speed CPU board have its own graphics output, but still being able to rely on local physical interfaces like Keyboard, SIO, PIA-ports, etc..
  6. Beautiful. Will test as soon as I reach my retro-desk!
  7. Well, finally caught a rather elusive bug that kept creeping from time-to-time on my screen. It seems worth correcting, for sure. Not sure if this has been already reported by other means, but here's the summary, after being able to reproduce it systematically (on INCOGNITO BIOS): Profiles 1,2,3 are XL/XE and profile 4 is Colleen. Go to, say, profile 2, then to HD/PBI sub-menu, and position cursor over Config.sys drive option. When cursor is there, ONLY press "4" (this will immediately move to Colleen profile, landing exactly on same sub-menu, where there is only ONE option). As soon as landing there, ONLY press "RETURN" key, and see what happens. If it is not possible to replicate above user-interface issue, let me know, and I will try posting pics. or video, or if more information is needed regarding my actual profiles configuration, not a problem, either. In addition to the above, I would like to mention that, if we attach .ATR images when navigating above profiles 1-3 and, after that, we move to profile 4, and then attempt to simply return to any 1-3 profiles, the .ATR images previously attached will be dropped IF and ONLY IF the non-Colleen profile sitting under 4th profile (Colleen) itself has PBI-BIOS disabled. This is easy to resolve, but it is worth noting, nonetheless.
  8. Second this one, completely... And get ready for a little "shocker": Booting a SDX Ultimage/SD or MaxFlash (1Mbyte) cart=image, from SIO-attached .ATR with config.sys, autoexec.bat, etc., plus RAMROD in 52K mode, I am able to load a (wrapped) special version of Avery's XEP80 Ultra-driver in the $C000-$CFFF region, with its own memory-manager, and, after everything is said-and-done, I end up with 37,200 Bytes of free SDX base RAM, AND 80-columns active (!) It all goes to show the 800's (unique) architectural flexibility, and how easy it is to expand its functionality, cleanly and neatly, and by keeping the base 800-HW essentially intact (!)... It's virtually plug-and-play, with no need of PBI-bus, and it all remains nicely tucked inside the expansion bay! ...just like a pregnant goose! 😜😉💪
  9. YES! The first time I noticed a bit of "color creep" on B&W y/c output was looking closely at System's Information wallpaper (when you boot it with enough base-ram). Then with a couple of utilities for testing Artifacting, with pre-configured odd-and-even horizontal patterns... And then I saw it again yesterday, when looking at Fractari's B&W output... It is not color aliasing per-se, but it is a luminance-driven induction of (residual) color-response. And as for what we are seeing here via Composite. here's PM-2.0, ran on my Vizio LCD TC, Sony Bravia large-screen TV, and [VP950b Monitor + DVDO iScan HD+ processor], ALL of them via COMPOSITE inpute: VIZIO: Sony Bravia LCD display: Viewsonic VP950b (95% of NTSC gamut) + DVDO iScan HD+: Notice that on the Bravia's picture, my iPhone's white-balance struggled hopelessly in the presence of strong natural back-light invading the living room. Image shifted all the way to the cool side, non-correctible during capture (it appears much warmer and closer to the other two, to the naked eye). So there you have it: Three different implementations, three different sources, three different years... all yielding the exact same result... This is NO coincidence.
  10. I really would like to see this (as well as all Fractari samples posted so far) done on the C64.... as well as the computing times... 😎😉
  11. Oh, yes, and it works beautifully! It improves the image noticeably, both spatially and colorimetrically.
  12. Consider using Flop's image as a test, since we have the results from several sources on this thread. Let's see the filtering effect on it, and compare with samples already posted.
  13. Glad to see we are both seeing the exact same results... over two entirely different video-paths, and terminal displays, as well. I've come to the conclusion that NOT being able to reproduce this effect over composite input may probably be a shortcoming or deficiency, instead of just a favorable mishap. We'll see what others see... (PS: I like that JVC... 750 lines horizontal... not bad at all!)
  14. Jeff: Just wanted to close the loop on this one. After good testing of the card, I am happy to report that it DOES NOT block the right-cart port, in any form or shape (contrary to my Intec card). It works like a charm, and (even better), it does so with my Newell's RAMROD personality card, too (!) I also rotate the hook-up pin on the RAM card about 90 degrees, so the signal pick-up cable could be routed sideways back to the RAMROD, thus making it disappear and enabling free insertion and extraction of RAM-board on Slot-1. Cheers!
  15. It may sound ironic... but this whole thread got me to re-think this issue entirely... especially after reading your explanations (and Fish's) and reasoning over it. Would it be that (what we are seeing happening with these images through NTSC-composite) the result of Artifacting or, instead, chroma / PAL-like blending... or a actually a cocktail of both? As for my own position, I am no longer sure it is artifacting... Funny, I may have to probably re-name the title of this thread! 😳😜
×
×
  • Create New...