letzter Beitrag von Freddy am
Alles anzeigenBtw, just for curiosity if anyone would like to test: https://github.com/lgblgblgb/x…s/tree/binary-windows-dev
Does it make any difference compared to the "stable branch" of xemu?
Also please note, that any test I can even do, is windows 10 based (though the original report from MadZ28 mentioned win10 as well, so maybe that's not the problem here).
Thanks for the reports and test so far, anyway!
Same error.
Ist there a way to manually create the SD-Card image?
Ist there a way to manually create the SD-Card image?
You can download a img file from the github site:
https://raw.githubusercontent.…e-for-xemu-xmega65.img.gz
Expand it, rename it to "mega65.img" and copy it to the correct path in your user profil:
Alles anzeigenIst there a way to manually create the SD-Card image?
You can download a img file from the github site:
https://raw.githubusercontent.…e-for-xemu-xmega65.img.gz
Expand it, rename it to "mega65.img" and copy it to the correct path in your user profil:
Sitzt, passt und hat Luft 
Alles anzeigenIst there a way to manually create the SD-Card image?
You can download a img file from the github site:
https://raw.githubusercontent.…e-for-xemu-xmega65.img.gz
Expand it, rename it to "mega65.img" and copy it to the correct path in your user profil:
People should stop using that, since it's a very old image and can cause serious compatibility problems (it's for an ancient version of Xemu). I will delete that, since it's kinda dangerous that people still like to download that :-O Actually I've deleted. however, please note dear Snoopy, that it's not personal or so, you're a very valuable that always ready to have opinions, helps, bug reports, etc, thus help Xemu become better and better 
Probably you can still re-use that file, if you at least re-fdisk, re-format and re-update the image at least after this step (this can be done with using only Xemu and its GUI no need for other tool). The process is written in the help (Ie -> right click inside the emulator window and select "help" it should open a web page with s link 'quick start' there).
Still, the real problem remains since this is surely a bug, I must solve somehow 
Workarounds are just ... well ... workarounds
People should stop using that, since it's a very old image and can cause serious compatibility problems (it's for an ancient version of Xemu). I will delete that, since it's kinda dangerous that people still like to download that :-O
Probably you can still re-use that file, if you at least re-fdisk, re-format and re-update the image at least after this step (this can be done with using only Xemu and its GUI no need for other tool). The process is written in the help (Ie -> right click inside the emulator window and select "help" it should open a web page with s link 'quick start' there).
Still, the real problem remains since this is surely a bug, I must solve somehow
LGB-Z
Btw, just for curiosity if anyone would like to test: https://github.com/lgblgblgb/x…s/tree/binary-windows-dev
Does it make any difference compared to the "stable branch" of xemu?
Yes it did make a difference!!! And I do run NTFS file system with enough room.
The mega65.img file was created on C:\Users\madz2\AppData\Roaming\xemu-lgb\mega65
The mega65.img file was created on C:\Users\madz2\AppData\Roaming\xemu-lgb\mega65
Yes, this method works as well, however it's much more easy if you use Xemu's GUI for this task, and also the second task, where it helps you to put the ROM image onto your card. Documented here: https://github.com/lgblgblgb/xemu/wiki/MEGA65-quickstart (this is the page you can access from the "Help" option as well from Xemu/MEGA65). But to summarize: you only need right click into the emulator's window and select SD-card -> format/fdisk stuff, then you download the ROM image yourself (here is the problem I can't automatize, since it's can be a legal/law problem, since it's a copyrighted thing ...) and then select SD-card -> update, which will ask you the ROM file, and you're done.
LGB-Z
Btw, just for curiosity if anyone would like to test: https://github.com/lgblgblgb/x…s/tree/binary-windows-dev
Does it make any difference compared to the "stable branch" of xemu?
Yes it did make a difference!!! And I do run NTFS file system with enough room.
Hehe, that's funny. Since when I wrote this question it wouldn't help, I guess. Just since then I came with a solution and committed into the dev branch, so I guess you used that, that's why it worked. Anyway, that's great since I wanted to ask you if you can help to test, but it turned out now you use that already, so no need task again for another version. Btw it was a problem with large file support (>2gbyte) in windows works a bit tricky, and Xemu is a multi-platform software need to support at least mac/windows/linux the same time. Anyway, thanks for sharing this information. I'll merge that change back to "master" (=stable) branch soon, so other users hopefully can benefit from that too.
After the mega65.img file was created I reintalled the master binaries executable to use the mega65.img but had some errors about needing 65 mb. So I went back to your install executable version and ran the SD update and is working now.
Thanks for your greatly appreciated help!
After the mega65.img file was created I reintalled the master binaries executable to use the mega65.img but had some errors about needing 65 mb. So I went back to your install executable version and ran the SD update and is working now.
Thanks for your greatly appreciated help!
OK! About the screenshot if you wonder: "DEMOEMPTY" disk is installed by Xemu (this is needed since there should be some default floppy disk image to be able to overriden with user's setting then). But surely you can use command line or the pop-up menu to attach other D81 images to use that. And btw, you can use "DIR" command in BASIC10 instead of loading "$" and LIST, still works, surely, but BASIC 10 gives some easier and faster method (also DIR does not destroy the in-memory BASIC program so you can write your BASIC program, and say "DIR" without loosing it ...).
Dev branch has been merged into the master. Hopefully it solves the problems of SD-card image related file I/O operations on Windows. I'm still unsure why I couldn't reproduce this bug, which seems to be there everywhere (on Windows), but whatever Thanks guys to post about it thus catching bugs & helping the development.
Downloaded the new stable zip and started xmega ..
Yeah this time he creates a 4GB img File
But when I choose 1) and enter config after that i have a strange Mousepointer
Anyone else having this Problem?
BTW.. How do i get back later to this config menu again after installation?
I can tell you how you get into the menu on a real MEGA65, it might be the same for the emulator.
Normally when powering on you press and hold the "ALT" Key on the MEGA65 keyboard (not sure if XEMU has the same mapping) this let's the MEGA jump into the configuration selection screen (1. SD Utility / 2. Configuration).
with this strange "mouse pointer"i don't have a clue, since the MEGA65 is not using a mouse there...
Alles anzeigenDownloaded the new stable zip and started xmega ..
Yeah this time he creates a 4GB img File
But when I choose 1) and enter config after that i have a strange Mousepointer
Anyone else having this Problem?
BTW.. How do i get back later to this config menu again after installation?
Mouse pointer: indeed, quite possible, this is an Xemu/MEGA65 bug (only 99.99% since another problem that Xemu uses a kinda old Hyppo, but newer ones new things to be emulated at hardware level to be able to run), however it does not even worth to track these kind of things down currently ... This is because VIC-IV (or III or II ...) emulation in Xemu/MEGA65 is very rudimentary, especially in case of sprites but many other things. Currently, even right now (while I'm typing this response), there are major efforts to totally rewrite video emulation related parts in Xemu/MEGA65 by myself and since a while by another developer joined. I wouldn't even try to solve these problems right now, since according my experience, it always ends in the problem of "incomplete emulation of VIC things" kind of area which can be solved only at a level of total rewrite. Which is an ongoing (not exactly a "small") effort. Thus, I'd like to ask patience with things like this, probably almost everything related to video/VIC/etc. Thanks!
I can tell you how you get into the menu on a real MEGA65, it might be the same for the emulator.
Normally when powering on you press and hold the "ALT" Key on the MEGA65 keyboard (not sure if XEMU has the same mapping) this let's the MEGA jump into the configuration selection screen (1. SD Utility / 2. Configuration).
with this strange "mouse pointer"i don't have a clue, since the MEGA65 is not using a mouse there...
MEGA65 does have mouse there, I've just tried it to confirm that (I can even use it with an Amiga mouse connected to the joystick port - I had to test this since I was not sure if should be mouse cursor in configure or not ...), so I'm quite sure. Maybe the reason of the problem in Xemu (the non-sense mouse cursor) that it's a 16 colour sprite (or other enhanced feature not emulated well enough by Xemu/MEGA65 yet), which is not emulated yet by Xemu/MEGA65, see my previous post here, about the emulation problems of VIC/video related things.
About accessing configure in Xemu: first of all, is kinda useless in case of Xemu, since many of the features are controlled by the emulator in contrast of a real MEGA65. But you can access it. It's a bit awkward because of the nature of an emulator: it's hard to do keypress so fast after starting the emulator, at the other hand if you hold a key BEFORE starting the emulator, it won't be sensed, since emulator does not run yet to get the keypress SDL event. This is a general limitation of an emulator, not so easy to give a solution, maybe I will introduce an Xemu menu point to achieve the goal. Anyway, indeed, it's holding ALT on MEGA65 while power-cycle it. In case of Xemu, it must be the right ALT key with the default keymap, as the left ALT is mapped to the MEGA key.
MEGA65 does have mouse there, I've just tried it to confirm that (I can even use it with an Amiga mouse connected to the joystick port - I had to test this since I was not sure if should be mouse cursor in configure or not ...), so I'm quite sure. Maybe the reason of the problem in Xemu (the non-sense mouse cursor) that it's a 16 colour sprite (or other enhanced feature not emulated well enough by Xemu/MEGA65 yet), which is not emulated yet by Xemu/MEGA65, see my previous post here, about the emulation problems of VIC/video related things.
Really ? Didn't know that. Something i gotta test later... ...learn every day something new. Thanks LGB-Z
MEGA65 does have mouse there, I've just tried it to confirm that (I can even use it with an Amiga mouse connected to the joystick port - I had to test this since I was not sure if should be mouse cursor in configure or not ...), so I'm quite sure. Maybe the reason of the problem in Xemu (the non-sense mouse cursor) that it's a 16 colour sprite (or other enhanced feature not emulated well enough by Xemu/MEGA65 yet), which is not emulated yet by Xemu/MEGA65, see my previous post here, about the emulation problems of VIC/video related things.
Really ? Didn't know that.
Well, the funny thing: I was surprised as well, "wow do we have mouse cursor there? Hmmm, let me check" And btw thanks for deleting my double post. It's really annoying, since forum64's engine seems to remember a draft even after writing/posting it, and if I hit that again by incident, I have a double post. Especially if I use multiple browser tabs :-/
hmmm... Is there a compiled windows version available ?
hmmm... Is there a compiled windows version available ?
Yes. With installer, or as a zip file (exe's and dll only) 32 bit or 64 bit versions. https://github.lgb.hu/xemu/
Though please note, that some user told me, the installer was found as trojan with some virus scanner, but it's probably because nullsoft installer use compression and other tricks, it's even documented in nullsoft's page, that these are all false alarms. Anyway, in case of any doubts, some can stick with the zip based version then ...
