Bill Brendling's version of MEMU

Everything about Andy Key's great Emulator MEMU
jonesypeter
Posts: 9
Joined: 08 Jul 2020 19:52

Bill Brendling's version of MEMU

Post by jonesypeter »

Greetings,

Is there anyway with Bill Brendling's version of MEMU to make the visible screen larger (To expand or zoom it)?

http://primrosebank.net/computers/mtx/e ... htm#CfgDlg

I have looked in memu.cfg and -vid-win-big is already set.

-vid-win-big,-v make window twice as large (realistic size)

I'm on a 2560 x 1440 display, so it still looks very small.

I will try the Raspberry Pi version over the weekend, which I believe is full screen.

Thanks
User avatar
Dave
Posts: 1327
Joined: 11 Aug 2012 18:16
Contact:

Re: Bill Brendling's version of MEMU

Post by Dave »

Hi,

thanks for posting here, I'm sure Bill will reply in due course.

In the meantime, have you tried adding a second -vid-win-big parameter? They are normally additive (is that a word?) in MEMU, i.e., adding it a second time makes the screen twice as big again

regards
Dave
jonesypeter
Posts: 9
Joined: 08 Jul 2020 19:52

Re: Bill Brendling's version of MEMU

Post by jonesypeter »

Thanks Dave,

Result! That worked. Thank you.
User avatar
Dave
Posts: 1327
Joined: 11 Aug 2012 18:16
Contact:

Re: Bill Brendling's version of MEMU

Post by Dave »

Great - glad it worked

If you haven't tried it, add it 3, or even 4 (or more) times to really blow it up.

I guess there's a balance to be struck between screen size and how big you want each of the possible 256x192 (in graphics mode) pixels to be

regards
Dave
Bill B
Posts: 641
Joined: 26 Jan 2014 16:31

Re: Bill Brendling's version of MEMU

Post by Bill B »

My Bare-Metal and Frame-Buffer versions of MEMU use the largest integer multiple of pixel size that will fit within the full screen.

The Microsoft Windows and X-Windows (Linux) versions work the same way as Andy's original. Each repetition of -vid-win-big (or -mon-win-big for the 80-column output) increments the scaling of the pixel size.
User avatar
gunrock
Posts: 276
Joined: 28 Oct 2020 21:17

Re: Bill Brendling's version of MEMU

Post by gunrock »

Small question for Bill, I see there's some source code to do with MFX emulation, does that include the network ports? And also does it work under Windows? One of the commit messages on the NFX code mention MFX support, so I'm guessing the NFX used the same Wiznet hardware (and same ports?), thus MFX networking might be enabled by the NFX code?
Steve G
Danish Memotech MTX 512, MFX and loving it
Bill B
Posts: 641
Joined: 26 Jan 2014 16:31

Re: Bill Brendling's version of MEMU

Post by Bill B »

gunrock wrote: 25 Jan 2025 14:31 I see there's some source code to do with MFX emulation, does that include the network ports?
Yes. Depending upon which network ports are being used, you may need to either run MEMU as root, or re-map the network port to an unprivileged port number using the -nfx-port-offset switch,
gunrock wrote: 25 Jan 2025 14:31 And also does it work under Windows?
No :( Widows networking is different to Linux, and I have not (at least yet) got around to writing a Windows version of the code.
Martin A
Posts: 840
Joined: 09 Nov 2013 21:03

Re: Bill Brendling's version of MEMU

Post by Martin A »

gunrock wrote: 25 Jan 2025 14:31so I'm guessing the NFX used the same Wiznet hardware (and same ports?), thus MFX networking might be enabled by the NFX code?
NFX was just a test of the concept, so there were actually 2 different WIZnet boards used in the NFX. The WIZ811MJ with a W5100 in the first couple of test boards and WIZ810SMJ with a W5100S in the last one. Software wise, in the configuration NFX (and subsequently MFX) uses, the W5100 and W5100S identical, physically they're very different.

The WIZ810SMJ was both easier to fit and cheaper, so that was the board that made its way to the MFX.

The NFX uses a different set of I/O ports, which were changed for the MFX at Andy's suggestion becasue of a potential clash with floating point accelerator.
Bill B
Posts: 641
Joined: 26 Jan 2014 16:31

Re: Bill Brendling's version of MEMU

Post by Bill B »

Martin A wrote: 25 Jan 2025 15:22 The NFX uses a different set of I/O ports, which were changed for the MFX at Andy's suggestion becasue of a potential clash with floating point accelerator.
Oops, forgot that :oops:

Had a quick look at the MEMU source code and by default it uses the original 0x90 to 0x93 ports for the Wiznet emulation. It does use a #define statement (NFX_BASE) to set the address, so easy to change when compiling.

Since MEMU does not emulate the floating point accelerator, there is no reason why it could not respond to either set of addresses.
Bill B
Posts: 641
Joined: 26 Jan 2014 16:31

Re: Bill Brendling's version of MEMU

Post by Bill B »

I have just pushed a minor tweak to the code. If building with MFX emulation enabled (which it is by default), the correct port addresses 0xA0 to 0xA3 are now used for the Wiznet emulation. If building with NFX support but without MFX, then the original addresses are used.

The other possible good news for Windows users is that I have an experimental version of MEMU using the SDL library rather than XWindows. I am working on this to provide Wayland support for when Linux distributions drop support for XWindows. This version includes NFX emulation, making use of the SDL networking routines. SDL is a cross platform library, so the same source code should build and run on Microsoft Windows, although I have never tried that.

The source for the SDL version is already in my repository, but it has had very little testing. To build the SDL version on Linux:

Code: Select all

git clone https://github.com/Memotech-Bill/MEMU.git
cd MEMU
mkdir build-sdl
cd build-sdl
cmake -DTARGET=SDL ..
make
The CMakeLists.txt file will probably need a bit of adjustment to build on Windows.
Post Reply