|
Post by cbmguy on Nov 13, 2023 17:31:29 GMT
Basic-128 v1.03 is the one you want - it was the latest that was published and probably on the net somewhere. Pokefinder.org maybe?
|
|
|
Post by cbmguy on Nov 18, 2021 4:40:19 GMT
I put it in the function rom setting and select ROM. default boot the c128 into 80 column mode (f7 in a positional keyboard setting). Then reset with the f3 key pressed for a positional keyboard or the alt key for a symbolic keyboard. The boot screen should say WALRUSOFT BASIC 8 100861 BYTES FREE. That's when you know the rom is loaded and ready to roll.
Cheers, ~ c
|
|
|
Post by cbmguy on Feb 7, 2020 13:37:40 GMT
Cheers!
|
|
|
Post by cbmguy on Jan 30, 2020 13:42:07 GMT
I am so looking forward for this to happen.
|
|
|
Post by cbmguy on Dec 12, 2019 14:35:58 GMT
If you read the memory address of a 1541, they are stored here. 1571 would be the same. I was looking at this a while ago and didn't find a universal method so I thought of making 'drivers' for each drive, sharing what I could as core disk drive procedures amoung them. That method would mean transfering blocks of data at a time yourself and controlling that data as it happens -- rather than relying solely on the kernal stuff for automating it all. I don't have access to my 1581 books right now, so I'm not too sure what those address in its ROM would be. The track/sector can be read from the block, itself, as well, which makes things a little more universal in regards to coding a core set of universal functions. I've used that last method when using some low level burst protocals -- the first block using burst can be a little buggy depending on the amount of data in the block on the sector... I'm rambling... sorry. 1541/71: $0016-$0017 Header ID from header of sector last read from disk. $0018-$0019 Track and sector number from header of sector last read from disk. m-r would do the trick for you. ist.uwaterloo.ca/~schepers/MJK/ascii/1541map.txt~ c
|
|
|
Post by cbmguy on Aug 20, 2019 19:08:19 GMT
I think there is enough room in the ROMs to make this work, however VICE doesn't support Interlaced mode at all, and Z64K doesn't seems to support custom ROMS =.= Are you sure? I can add both pal and ntsc kernals along with custom roms for the drives, as well. Jiffy roms work fine with it so I'd imagine other roms would, as well.
|
|
|
Post by cbmguy on Jun 13, 2019 12:42:19 GMT
It's a remote Graphics viewer and monitor for VICE by the looks of it. Run this application on your windows box, run VICE, select 'enable external monitor" from teh machine settings and you're golden. From there, you can select a page for the VIC to view or VDC now and some source code which you can debug in real time. I loaded up turrican II and selected VIC bitmap then selected $E000 for the page. The app showed the VIC screen remotely, for example. I tried to load up Wheels128 to see the boot loader source and the VDC bitmap display, but it would never connect and kept crashing. Even with just the normal bootup screen it would simply crash I've only been able to connect once, however. Pretty slick if it was more stable or perhaps I was starting them up wrong ... or something... ??
|
|
|
Post by cbmguy on Jun 7, 2019 14:15:08 GMT
|
|
|
Post by cbmguy on May 30, 2019 17:59:03 GMT
They work great. 1541UII REU, CMD HD Native Partition, C128 w/64k VDC. Installed off a 1571 perfectly fine. Booted from the CMD native partition perfectly.
|
|
|
Post by cbmguy on Feb 26, 2019 15:38:45 GMT
I had some questions about 'nightly builds' like the winvice bin's. I'm not too sure what the official process is, but I'd head over to sourceforge and checkout the latest trunk: sourceforge.net/p/vice-emu/code/HEAD/tree/Before step 2, above, I'd cd into that new trunk directory and then as root, issue an ./autogen.sh. Once that has completed, proceed with step 2 onward. You should have the latest source push compiled and ready to go. Your milelage will vary depending on what issues have crept in with the new source. Cheers, c
|
|