|
Post by cthulhu on Jul 29, 2014 7:43:17 GMT
I assume you switch in the VIC signal on the composite/sync line in 40-column mode... but how did you drive composite/sync when it was in 80-column mode? In 80-column I'm using the (monochrome) composite signal from pin 5 of the RGBI output (connected to pin 20 on the SCART connector) to drive sync.
|
|
|
Post by cthulhu on Jul 25, 2014 9:01:02 GMT
Last year I built almost the same cable (thanks hydrophilic for your pull-both circuit!), but I added a switch to have 40 column composite signal on the SCART as well. I didn't put 1K resistors on the +5V line, in my case I seem to not need them, but that it could be just me. What I found to be really usefull was to swap the 1K and 1.2K resistors in the pull-both circuit with 1K variable resistors as with the "default" ones colors was too feeble. That way I could adjust the intensity of each color.
|
|
|
Post by cthulhu on Jul 11, 2014 11:24:00 GMT
I hope he hasn't become completely discouraged. I'm cheering for him! In his blog he said that he's back at work and I'm really eager to see what the first live version will look like.
|
|
|
Post by cthulhu on Jun 24, 2014 8:18:32 GMT
So I guess SD2IEC supports DNP? Still I don't think it supports D1M / D2M / D4M images. Yes, SD2IEC seems to support DNP, but in order to use it with GEOS (ie boot from a .DNP disk image, apparently works for Wheels only) you should first load into your SD2IEC a (fake) CMD-HD ROM via this command: @"XR:FAKEHD.BIN" This is needed because GEOS (Wheels) performs a more through scan of device rom (via M-R operations) to detect a drive type, and the standard mechanism supported by the SD2IEC firmware is not sufficient in case of CMD_HD emulation. Fake CMD-HD and CMD-FD roms can be downloaded from SD2IEC firmware site.
|
|
|
Post by cthulhu on Jun 24, 2014 8:03:33 GMT
Werner Weicht released UIEC-Manager for GEOS some 2.5 years ago Thanks Tokra! Yes, that's the same software I was referring to in my first post.
|
|
|
Post by cthulhu on Jun 23, 2014 15:28:33 GMT
If geos has a device driver made for it, It should work Yes, that's what I was thinking, but I've never seen any mention about a SD2IEC/uIEC native GEOS driver. The closest thing I've seen was a youtube video of Wheels128 in which you could distinguish an A: device with the icon of a CMD-HD named "sdiec".
|
|
|
Post by cthulhu on Jun 23, 2014 14:45:08 GMT
I'm not talking about running GEOS from a SD2IEC, but using a SD2IEC (not as D64/71/81 disk image, but as the real device: browsing its tree structure, mounting / unmounting disk images found there, launching programs, etc.) under GEOS. Is there any setup / programs which can do it? The only one I'm aware of (after googling around a bit) is this one, anyone has ever tried it out?
|
|
|
Post by cthulhu on Jun 20, 2014 13:48:28 GMT
Thanks a lot, it will be really useful once completed!
|
|
|
Post by cthulhu on Jun 10, 2014 11:08:07 GMT
Also, Mirkosoft told me of very simple test: SYS52698,,28 : RREGA (63 = 64kB / 47 = 16kB) But that method relies on the VDC register being set correctly by KERNAL. I don't think it is set to 64K if user upgraded their system from 16K. However, I have no way to test this on real hardware. I have exactly this config: flat C128 with 64K VDC RAM upgrade. Yesterday I tested Miro's method and it reported 47 (16K), so no, it doesn't work on upgraded systems.
|
|