[Coco] Beta release 1.0 Windows of OVCC

[Bill Pierce]

Walter, I tried the Windows version and get errors on missing DLLs, which I assume are the ones in the DLL folder. Do these files need to be relocated somewhere?
 
 
 
-----Original Message-----
From: Walter Zambotti <zambotti at iinet.net.au>
To: 'CoCoList for Color Computer Enthusiasts' <coco at maltedmedia.com>
Sent: Wed, Jan 2, 2019 12:09 am
Subject: [Coco] Beta release 1.0 Windows of OVCC

Announcement.

 

I have released the first Beta version of OVCC for windows.

 

https://drive.google.com/drive/folders/1xL8jWnwWLKL9D6K5ZNHIYRGNySIipEKV?usp
=sharing

 

The only modules ready are :

 

MPI

HardDisk

OrchestraC90

 

The other modules are coming within then next week.

 

The Linux version will be released within the next few days.

 

Using.

 

Download the contents of the entire Windows folder to some location.

 

To just test it use the ovcc.bat file to launch.  (However it does create a
DOS cmd window)

 

To use the ovcc.exe directly the dlls in the dlls subfolder will need to be
copied to a location on the PATH. Normally where are windows dlls are
maintained. C:\Windows\System32 is  good candidate.

You shouldn't copy the dlls to the same folder as the exe itself as loading
module dlls from within ovcc becomes confusing.

 

If you already have SDL2 2.0.8 or later installed on your PC you won't need
to install the one I supplied.

If you already have AGAR 1.5.0 installed then you will need to ensure the
ones I supplied are located before your current AGAR install.  The AGAR libs
supplied are not the same as those available on the internet.  Several bugs
have been fixed and special features added to support OVCC.

 

The supplied Vcc.ini is setup for:

 

MPI:

 

SLOT4 : HardDisk

SLOT3 : Orch90

 

HardDisk: VCCemudisk.vhd (the vhd has not been supplied).

 

If you supply ROMs they should go in the same folder as the executable.

 

Caveats.

 

Some features are not supported and will let you know if you try to activate
them:

 

Turbo CPU

MMU support

 

Other features are not supported because they weren't actually provided in
VCC 2.01B:

 

Hires mouse

 

Other features are not supported as I have no hardware to test them:

 

Analog Joysticks

Physical Floppy Drives (for when the floppy module is released in the next
few days)

 

Instability.

 

Generally the system is stable after you have made all your setup changes.
However the menuing system intermittently causes crashes.

 

However after performing all your setup using the menuing system the
emulator core is quite stable.

 

So as long as you use the emulator for its core function and not to exercise
the menus it runs well.

 

Keep an eye on the frame counter on the message bar.  It should remain
around 60 (59) fps.  If it starts dipping  flickering for no apparent
reason* you will begin to experience audio drop outs.  When this happens a
restart will be required.  However this normally only happens after playing
around in the menus.

 

If you leave the configuration dialog window open you may also experience
frame rate loss. Close it!

 

*No apparent reason is not when you crank the CPU frequency up beyond the
capabilities of your PC.  This is an apparent reason.  Just turn it down!

 

The source code (which I am still working on) is located at:

 

https://drive.google.com/drive/folders/15e21fjAziBo4GTMhYTgP_XGMZ-3u844b?usp
=sharing

 

The source code is the same between the Linux and Windows version.

 

Enjoy.

 

I suppose reporting bugs should go directly to me to avoid CoCo list
congestion.

 

zambotti at iinet.net.au <mailto:zambotti at iinet.net.au> 

 

Regards

 

Walter


-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco