(from old issues page)
BGPierce commented on Jan 7, 2016
Does anyone know if the "ramdisk.dll" actually works? I have never tried this module. I think it is supposed to be an emulation of Disto's Ram cart. If it actually works, I would like to document it's use and include it in the release.
I will look into this a little more.

(from the old issues page)
msmcdoug commented on Sep 14, 2016
Seems there is an incompatibility between Vcc and MAME/MESS for 32KB ROM images.

MAME/MESS want a naturally-ordered ($8000-$FFFF) 32KB block whereas Vcc requires that the top and bottom 16KB blocks are switched ($C000-$FFFF,$8000-$BFFF).

Whilst archives on the net tend to be in the swapped format (Vcc) and therefore incompatible with MAME/MESS, it's worth noting that this swapped format is also unsuitable for burning to FLASH/EPROM.

I would argue that the naturally-ordered format is easier to produce for developers, compatible with MAME/MESS and FLASH/EPROM burners. Should we also change Vcc to use this format?

(from old issues page)
BGPierce commented on Jan 8, 2016
VCC has always needed a debug function. Again, a good example is the Mess debugger.
When turned on, a separate window opens showing the current address being accessed (scrolling) and a representation of the asm ascii and hex code... kind of like ZBug.
You should be able to set breakpoints, single step etc...

Like this:

(from old issues page)
BGPierce commented on Dec 29, 2015
I have had many people tell me that the artifact colors in composite mode on the Mess Coco emulator are much truer than the artifact colors in VCC's composite mode.
Since we are basically rewriting this stuff, maybe we could take a look at the Mess sources and see how they implement the artifact colors to get an idea on how to improve VCC's artifact colors.
The "Gamers" would love it.
Any thoughts?
B.P.

While upgrading to 2.1.0d , I noticed several typos and other potential problems in the attached pdf file of the Welcome manual. Each such spot is identified by semi-transparent red highlighting along with an associated sticky note. The annotations were placed from within Adobe Acrobat Reader DC, running under Windows 10 Pro.

Welcome to Vcc 210d Typos.pdf

If you alt-tab away to another application VCC thinks you pressed the ALT key. It's a minor annoyance, but in (Nitr)OS-9 it puts the keyboard in some kind of graphics character mode.

(from the old issues page)
BGPierce commented on Jan 10, 2016
On the latest build (01/09/2016), when VCC is in full screen mode, if you hit the "Windows" key (start menu), VCC will crash. It should go back to default size OR just minimize. It tries to stay on screen with the windows startbar and start menu....

(from the old issues page)
BGPierce commented on Dec 29, 2015
Something that was brought to my attention was the way VCC's menu system works.
In Mess (and other emulators including XRoar), when a system menu is open, the emulation "pauses" and waits for you to exit the menu.
In VCC, the emulation continues to run while any menu is open. I have found this to be both an advantage as well as a hinderance.
Any thoughts on this?
B.P.

The Tetris (Tandy version btw) game is unable to be controlled with the keyboard. The keys are inputting things all over the place, making the game unplayable as a result. I'm sorry I can't explain this any better, but my English is limited.
I tried with different keyboard layouts, different regional layouts, different physical keyboards (I'm on a laptop without a number pad) but keyboards inputs are still wrong. I can only assume the emulator is the culpirit here, which is quite something to say for a quote "accurate CoCo 3 emulator". Any ideas?

Fatal error message should pop up if -i option is used to specify a config file that can not be opened for write to alert user that he is trying to use an unworkable config file. Vcc should then exit.

(from the old issues page)
BGPierce commented on Dec 29, 2015
In the "Configuration/Joysticks" tab, there are check boxes for the :
"Standard"
"Tandy HiRes"
"CC-Max"
hires interfaces. These were added by Joe, but never completed. At the moment, the functions are disabled. It would be nice to see these joystick hires interfaces implemented.
B.P.

(from old issues page)
ursine commented on Dec 14, 2016
The VCC code base is currently made up of a hybrid of C files and C++ files. The compiler decides which it is by checking the extension: ".c" gets compiled using the C compiler, ".cpp" gets the C++ compiler.

Currently VS 2015 does not completely support modern C and this causes some minor hand holding to be required. Changing all of the .c extensions to .cpp will cause the C++ compiler to be invoked, giving access to modern code features of C++11/14, as well as the use of the common subset of modern C.

It should be as simple as changing the extensions and submitting it, but there's always possible issues. I plan to do this shortly. (If there are any concerns please discuss soon)

(from old issues page)
BGPierce commented on Jan 7, 2016
In the "Config/Display" tab, if the "Throttle Speed" checkbox is unchecked, the emulator is almost unusable on todays fast computers. It makes key repeat (in OS-9) and mouse clicks repeat so fast, you cannot type or click on anything without it repeating beyond control.
When the CPU, or clock timer are running faster, the keyboard or mouse input should not be affected.

The error only occurs when saving to the same ini file. To prevent copying the ini file to it's self the code does a path compare. This fails when the paths point to the same file but differ in case. Using a compare that ignores case should fix the problem.

Bitdefender detected a virus within the .ZIP file when I extracted the files. Not sure if thats a false positive but somebody should probably take a look at it.

The file wimgtool-os9.exe is infected with Gen:Trojan.Heur.GC.O9Z@q9iuvriib and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean.

(from the old issues page)
jejones3141 commented on Apr 16, 2016
I believe that the declaration of FlagEmuStop should be changed to

static volatile unsigned char FlagEmuStop=TH_RUNNING;
because as it is, a compiler is free to change the loop

FlagEmuStop=TH_WAITING; //Signal Main thread we are waiting
while(FlagEmuStop==TH_WAITING)
Sleep(1);
in EmuLoop() to

FlagEmuStop = TH_WAITING;
for (;;)
Sleep(1);
since FlagEmuStop is static and its address is never passed outside Vcc.c.

I've been running Vcc on Linux using WINE, and I find that selecting exit doesn't close the Vcc window. I can't swear that this is the cause of the problem, but it could be. I don't use Windows (save under duress), and Visual Studio is in the "garbage" category at winehq, so I can't make the change locally and rebuild to test; sorry about that.

I tried clicking the wiki link (to get to the documentation referenced in the readme) but the link just redirects me to the current page:

Go to
https://github.com/VCCE/VCC
click the Wiki link (https://github.com/VCCE/VCC/wiki)

result:
I get directed back to https://github.com/VCCE/VCC

If you leave VCC running, and windows goes into screen saver mode, upon exiting screen save mode, VCC crashes.

(from the old issues page)
Luis46coco commented on Apr 13, 2017
C ++ writing format and user display formats

I think we should have a common site to share, discuss and reach agreements on internal and external formats, for example

I do not know if it is better (* .bin, * .dll) or with ";" Instead of "," and if you always add a space later or not, or use uppercase or lowercase letters

So far the format seems to be, lowercase and space after ","
I do not know if it's better, ";"

With respect to the c ++ format it seems a little long
command
{
Break;
}

I prefer

Command {
Break;
}

Or for a single instruction inside, use:

Command
Break;

BGPierce commented on Dec 29, 2015
Since I run VCC quite often (read A LOT!), I find I use the increased CPU speed ("Configuration/CPU") set to the max most of the time. This setting not only speeds the CPU, but also increases screen refreshes and graphics speed. To change this setting, you open the conifg menu.
It would be nice to use F4 (unused) to set "max speed" on first press, then "minimum speed" on 2nd press.
OR.. use F3 (also unused) to slow down the CPU by 10% on each press until bottomed out, and F4 to increase the CPU by 10% on each press until maxed out. This would allow people with slower computers that cannot handle "max speed" to at least take advantage of increased speed without opening the config menu.
Any thoughts on this one?
B.P.

(from the old issues page)
abcbarryn commented on Feb 3, 2016
It would be really nice to have an RS232 pak emulation that would connect to an IP and port address. That way I could use VCC to run terminal software or accept incoming connections without using a DriveWire server. DriveWire becker port support is nice, but having to run a server process just to get this ability is a pain.

Thank you for new version 2.0.1f.

Unfortunately it still shows version 2.0.1e - not a big deal but on the other side also not "nice".

Kind regards!

(from the old issues page)
BGPierce commented on Jan 16, 2016
This has really been an issue since VCC was started. In a hardware text screen, when issuing a "BlnkOn(stdout);" (in OS9), the following text should "blink" on and off. This is a function of the GIME chip as it only works on a 'hardware' text screen (40x24 & 80x24) and not on graphic text screens.
This would have to be implemented in the GIME emulation. I'm not sure is this is implemented in Mess or not. I think it is.

When Vcc starts with no ini file it creates a new one with default settings but the save screen size is set to on while the screen size is set to zero resulting in a poor user experiance on first start. If the Vcc.ini file is missing the window size should be set to 640x480 by default.

using the included floppy cart i tried to load and execute rupert rythm game.
There are 2 versions of this game on virtual disk available one won't load freezing the emulator the other loads but doesn't emulate sounds or graphics correctly.

(from old issues page)
Wersley commented on Jan 7, 2016
Add multiple switchable ROMs on SuperIDE, more like the real hardware. Allow selection of up to 4 ROMs and a switch to choose which is active.

(from old issues page)
ursine commented on Dec 16, 2016
Currently, the code is split into many plugins. Given that the system is now open source, having an external API is likely unnecessary. I would like to propose condensing the plugins into the main codebase. This would allow the compiler/linker greater insight into the code for optimization purposes, as well as reducing the system to a single exe rather than a bunch of dlls and an exe.
Thoughts/Ideas/Objections?

(from old issues page)
BGPierce commented on Jan 7, 2016
If you use “.wav” files, if the “.wav” file is not recorded in “8-bit, 44,100 khz”, VCC will mangle the file just by loading it, you don’t even have to “play” it. Most “standard” wave files are in 16-bit, 44,199 khz. These will not work in VCC and even if you just browse to them and select them into the tape interface, VCC will try to convert them to 8-bit and ruin the file. This applies ONLY to the wav format. The "cas" files are not wave formatted files and are not affected.

(from old issues page)
BGPierce commented on Dec 29, 2015
This will be where we can start listing the things we would like to see in upcoming revisions of VCC.
Not to say it's the "Coco 4" wish list where everyone wants 1024x728 display or 2 million colors, but instead listing simple things.... things more involved with the emulator's appearence and menus and not the Coco's enhancements.
I will start a list, then everyone can chime in with things they would like to see as well. You never know, some of it may come about and be part of the new VCCX !
B.P.

You can see the problem if you run this in Vcc:

10 WIDTH 32
20 PMODE 1,1
30 SCREEN 1,1
40 POKE &HFF22, 192
50 PCLS 1
60 GOTO 60

The problem is that the border is white. The border should be green, just like the middle.

As of 2.1.0b the emulator does not recognize the arrow keys in any of the 3 default choices.

EQU Ver 5 loads and runs. Problem is VCC is Write Protecting it. Can not make directories. get Error 242 - Write Protect. Same if I try and save a text file. Drive 0 and Drive 1 also Write Protected.

(from the old issues page)
Wersley commented on Jan 10, 2016
VCC allows you to try to resize the window, but it does not work correctly. Resize should be disabled or scaling implemented.

(from old issues page)
Wersley commented on Jan 9, 2016
Add user interface to disable the RTC in the HardDisk module.

I'm running on Windows 10 Enterprise

When VCC starts, there are 2 copies of the DISK EXTENDED BASIC message

ptaylor1984 commented on Feb 6, 2018
I would like to see the old Rs232 pack and some folks are showing more interested with running a bbs system. Using the same functions and features of the old Rs232 Pack would save from having to write several hundred lines of codes if it support the same memory address to receive, send and carrier detect. The incoming data control can be controlled using timer evens which most programing languages support to slow down the data to 9600 baud. So lets bring back the old bbs system because calling a bbs is not a real coco bbs unless its running on the Trs-80.

Can this emulator create floppy images from actually floppies from OS9 and RSDOS disks?

(from the old issues page)
BGPierce commented on Sep 2, 2016
In the current release (from vcc-1.200b, not the master), I've found that the "SuperIDE.dll" does not function. Everything seems to work up until it goes to read the drive on restart after making the proper setting in all the configs. I get the hdblba error "LBA Hard Drive Not Found", when there is a CF card image mounted.
I have tested these settings on both VCC 1.42 and VCC 1.43beta and the SuperIDE.dll works properly.
This may not be an issue once the latest commint is finally made as I know quite a few things are being rerranged.

Try it...blank screen...if you keep hitting your mouse it slowly shows the characters ...but does not run.

As the title says, would this be possible to avoid problems with user accounts (non-admin accounts), which have no write access for the config file(s)?

Setting the Joystick preferences, they don't seem to stay after exit and restart of VCC

If you try Hicolor2 and once its up...you press d and l and load a bmp thats 320x200x256 it looks bad....but
if you press a, b, c, then d then l and load the bmp the color is correct.

Is there any chance the files required for the Inno Script and the script itself can be added to the solution?

Where are mine + snowdogs issues? I think you had closed them but they don't show up at all ... I was just going to comment on snowdogs pull request about the appdata folder.

Even though the projects do not utilize MFC all resource files are referencing afxres.h for their Windows resource specific symbolics and afxwin.h for functionality. These header files and the associated libraries are part of MFC which is not included in newer versions of Visual Studio and thus may not be installed. Since there is no real dependency on MFC libraries (except for AfxInitRichEdit which should be changeD) use of those header files should be changed.

This should be changed to use winres.h and windows.h respectively to remove the dependency and allow easier building with newer versions of VS and other platforms (cross compile from GCC).

(from old issues page)
jaggies commented on Mar 2, 2019
While going back and forth between real hardware, I found VCC is tolerant of not clearing FIRQ/IRQ/NMI sources (e.g. forgetting to read GIME register 0xff93 to clear the interrupt). I had to break out the oscilloscope to figure out what was going on. :) Applications that are written correctly don't have a problem, of course, but it makes cross-developing code more challenging since code that works fine on the emulator locks up the real hardware.

I just discovered this project and it looks far, far more advanced than I would have expected. It even has HDD support and other things? This really brings me back!

It would be nice if Linus support were present because then we could make this work on a Raspberry Pi 400. From there, a bit of scripting and all that and I've got my old CoCo3 running OS9L2 and all of those things from decades ago. Really miss those days.

Getting Linux support would be a logical step to getting it working on Raspberry Pi hardware. Would donations of hardware help with the cause?

It's a little thing, but I used to enjoy "hearing" the data load into my coco (especially when loading madness and the minotaur, where you "hear" the graphical data loading while the screen is painting during the load).

however, in the emulator if I issue the "audio on" command followed by cload/cloadm/csavem/csave/csave"file",a I do not hear any cassette audio at all.

(from old issues page)
Luis46coco commented on Apr 14, 2017
The .pak cartridges have a header and a foot with information, which can easily be recognized and accepted, they are no longer used much, but it is easy to make them not block and run well, less problems for the new coco initiates.

.pak only serve for emulators in ms-dos, but it's easy to accept them.

Some time ago I made a converter

PRINT "Program for convert Color Computer Cartridge V.1.00 01/2011"
PRINT "By Luis Fernandez [email protected]"
PRINT "MS-DOS convert filenames to 8.3 and uppercase"
PRINT
PRINT "Use COCOPAK *.PAK *.CCC"
PRINT " or COCOPAK *.CCC *.PAK"
PRINT
PRINT "CCC to PAK"
PRINT " Add at first, 2 Bytes int len(arch) and 2 Bytes int &hC000"
PRINT " and at end, 33 bytes 0 (cero) and 2 Bytes int &hC000"
PRINT
PRINT "PAK to CCC"
PRINT " delete 4 bytes at first and 35 bytes at end"
END