Mazzspeed Posted September 8, 2021 Share Posted September 8, 2021 Wine replaces Windows API's to communicate with the Linux kernel as opposed to the NT kernel, you can't run Wine under Windows as technically there should be no reason to do so. Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted September 9, 2021 Share Posted September 9, 2021 unless you want to run something newer on an old version of windows since wine apparently mimics the newer version... anyway that's just an idea... if it were at all possible... Windows has always been a pain... but it's down to what they know... the nice thing about the fujinet bridge idea was that once it is set up, I could possible make certain directory(s) possibly read only so they can't goof it up so to speak Quote Link to comment Share on other sites More sharing options...
+x=usr(1536) Posted September 11, 2021 Share Posted September 11, 2021 Not a Windows user here, so my experience with Altirra is minimal to say the least. If this is a dumb question, at least you know why in advance Does Altirra (or any other emulator, for that matter) have the ability to attach to external devices via an SIO2USB or similar? The UDP bridge idea is also a good one, and I'm not proposing the SIO2USB route as a replacement for it. But as a complementary method, there are certain circumstances where having the option of physically-attached hardware would be beneficial. Quote Link to comment Share on other sites More sharing options...
Elkino Posted September 11, 2021 Share Posted September 11, 2021 1 minute ago, x=usr(1536) said: Not a Windows user here, so my experience with Altirra is minimal to say the least. If this is a dumb question, at least you know why in advance Does Altirra (or any other emulator, for that matter) have the ability to attach to external devices via an SIO2USB or similar? The UDP bridge idea is also a good one, and I'm not proposing the SIO2USB route as a replacement for it. But as a complementary method, there are certain circumstances where having the option of physically-attached hardware would be beneficial. I discussed something similar, with a SIO2USB cable with all pins it should be posible, as when you attach a 1050 drive to the PC to copy files to the emulator. https://github.com/atari800/atari800/issues/127 1 Quote Link to comment Share on other sites More sharing options...
+x=usr(1536) Posted September 11, 2021 Share Posted September 11, 2021 1 hour ago, Elkino said: I discussed something similar, with a SIO2USB cable with all pins it should be posible, as when you attach a 1050 drive to the PC to copy files to the emulator. https://github.com/atari800/atari800/issues/127 I'd love to see Atari800 integrate SIO2USB support; it's my go-to emulator on macOS and Linux. Having said that, there's a lot to be said for @tschak909's initial idea of running the FujiNet as an SIO2* device. It already does SIO passthrough, and with Bluetooth, WiFi, and USB as options, should be able to connect / bridge to just about anything. 1 Quote Link to comment Share on other sites More sharing options...
a8isa1 Posted November 23, 2021 Share Posted November 23, 2021 Connect FujiNet with NetSIO hub In FujiNet web interface, in Emulator settings enable SIO over Network option and fill in host name or IP address of computer running Altirra and hub. Save settings. Hi, apc! I was reading the instructions and came to the above section. I do not see this setting in the web interface. Is there a custom FujiNet firmware for this project? -SteveS Quote Link to comment Share on other sites More sharing options...
mozzwald Posted November 23, 2021 Share Posted November 23, 2021 1 hour ago, a8isa1 said: Is there a custom FujiNet firmware for this project? https://github.com/FujiNetWIFI/fujinet-pc Quote Link to comment Share on other sites More sharing options...
a8isa1 Posted November 23, 2021 Share Posted November 23, 2021 ah. thanks. names had me confused. when I saw FujiNet I thought this meant the physical device, having forgotten that the executable for Fujinet-PC is called "fujinet" Now next questions... Can all this be done from linux, Altirra running under wine and netsio-hub launched natively? I ask because I see the following things: SIO HUB v0.1 Listening for NetSIO packets on port 9997 Altirra Custom Device Server v0.8 Waiting for localhost connection from emulator on port 9996 -- Ctrl+Break to stop 14:40:57.317312 Device connected 192.168.1.214:46707 [1] -SteveS Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted November 24, 2021 Share Posted November 24, 2021 yep it's hard to find the right or correct item when it's named the same... Quote Link to comment Share on other sites More sharing options...
apc Posted November 26, 2021 Share Posted November 26, 2021 (edited) On 11/23/2021 at 8:42 PM, a8isa1 said: ah. thanks. names had me confused. when I saw FujiNet I thought this meant the physical device, having forgotten that the executable for Fujinet-PC is called "fujinet" On 11/24/2021 at 1:15 AM, _The Doctor__ said: yep it's hard to find the right or correct item when it's named the same... Yes, FujiNet is correct. The code is prepared for both FujiNet-PC as well for the hardware FujiNet ? The firmware with this code has not been released yet. Coming soon ... Edited November 26, 2021 by apc 1 Quote Link to comment Share on other sites More sharing options...
apc Posted November 26, 2021 Share Posted November 26, 2021 On 11/23/2021 at 8:42 PM, a8isa1 said: Can all this be done from linux, Altirra running under wine and netsio-hub launched natively? Yes! On 11/23/2021 at 8:42 PM, a8isa1 said: I ask because I see the following things: Current netsio.atdevice works with 3.90 and 4.00-testNN (same custom device file). The things has changed slightly with Altirra 4.00 release. It stopped to work in 4.00 release due to small workaround for 3.90: @phaeron not sure, if I am doing something wrong ^^^ It looks like thread in 3.90 is created but not switched into, waiting for next switch. Thread.sleep() helped me to switch. But this is guarded now ? Any idea for better solution? @a8isa1 For quick fix you can edit the netsio.atdevice file and comment out "Thread.sleep(400)" on lines 265 and 271: If I will not find a better way, I will prepare netsio.atdevice in two versions, for 3.90 and for 4.00. Jan Quote Link to comment Share on other sites More sharing options...
a8isa1 Posted November 26, 2021 Share Posted November 26, 2021 19 minutes ago, apc said: Yes! Current netsio.atdevice works with 3.90 and 4.00-testNN (same custom device file). The things has changed slightly with Altirra 4.00 release. It stopped to work in 4.00 release due to small workaround for 3.90: @phaeron not sure, if I am doing something wrong ^^^ It looks like thread in 3.90 is created but not switched into, waiting for next switch. Thread.sleep() helped me to switch. But this is guarded now ? Any idea for better solution? @a8isa1 For quick fix you can edit the netsio.atdevice file and comment out "Thread.sleep(400)" on lines 265 and 271: If I will not find a better way, I will prepare netsio.atdevice in two versions, for 3.90 and for 4.00. Jan apc, thanks for the additional information. I made the changes to netsio.atdevice. However, when I start up Altirra fujinet-pc kicks out with the following informaton in the debug log: 20:54:52.278 > Post_config request handler 20:54:52.278 > key="hsioindex" 20:54:52.278 > value="0" 20:54:52.278 > New HSIO index value: 0 20:54:52.278 > Set HSIO baud from 38400 to 125000 (index 0) 20:54:52.278 > fnConfig::save 20:54:52.278 > fnConfig::save wrote 452 bytes 20:54:52.289 > Opening file for parsing: '/www/index.html' 20:55:00.290 > SystemManager::reboot - exiting program with EX_TEMPFAIL code ... 20:55:00.290 > Shutting down device 50 20:55:00.290 > Shutting down device 40 20:55:00.290 > Shutting down device 45 20:55:00.290 > Shutting down device 70 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > Shutting down device 78 20:55:00.290 > Shutting down device 77 20:55:00.290 > Shutting down device 76 20:55:00.290 > Shutting down device 75 20:55:00.290 > Shutting down device 74 20:55:00.290 > Shutting down device 73 20:55:00.290 > Shutting down device 72 20:55:00.290 > Shutting down device 71 20:55:00.290 > Shutting down device 38 20:55:00.290 > Shutting down device 37 20:55:00.290 > Shutting down device 36 20:55:00.290 > Shutting down device 35 20:55:00.290 > Shutting down device 34 20:55:00.290 > Shutting down device 33 20:55:00.290 > Shutting down device 32 20:55:00.290 > Shutting down device 31 20:55:00.290 > All devices shut down. 20:55:00.290 > Shutdown handler called 20:55:00.290 > fnTaskManager::~fnTaskManager 20:55:00.290 > ### NetSIO stopped ### 20:55:00.290 > FileHandlerLocal::close 20:55:00.290 > delete FileHandlerLocal 20:55:00.290 > Stopping web service -SteveS Quote Link to comment Share on other sites More sharing options...
tschak909 Posted November 26, 2021 Author Share Posted November 26, 2021 Just now, a8isa1 said: apc, thanks for the additional information. I made the changes to netsio.atdevice. However, when I start up Altirra fujinet-pc kicks out with the following informaton in the debug log: 20:54:52.278 > Post_config request handler 20:54:52.278 > key="hsioindex" 20:54:52.278 > value="0" 20:54:52.278 > New HSIO index value: 0 20:54:52.278 > Set HSIO baud from 38400 to 125000 (index 0) 20:54:52.278 > fnConfig::save 20:54:52.278 > fnConfig::save wrote 452 bytes 20:54:52.289 > Opening file for parsing: '/www/index.html' 20:55:00.290 > SystemManager::reboot - exiting program with EX_TEMPFAIL code ... 20:55:00.290 > Shutting down device 50 20:55:00.290 > Shutting down device 40 20:55:00.290 > Shutting down device 45 20:55:00.290 > Shutting down device 70 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > disk UNMOUNT 20:55:00.290 > Shutting down device 78 20:55:00.290 > Shutting down device 77 20:55:00.290 > Shutting down device 76 20:55:00.290 > Shutting down device 75 20:55:00.290 > Shutting down device 74 20:55:00.290 > Shutting down device 73 20:55:00.290 > Shutting down device 72 20:55:00.290 > Shutting down device 71 20:55:00.290 > Shutting down device 38 20:55:00.290 > Shutting down device 37 20:55:00.290 > Shutting down device 36 20:55:00.290 > Shutting down device 35 20:55:00.290 > Shutting down device 34 20:55:00.290 > Shutting down device 33 20:55:00.290 > Shutting down device 32 20:55:00.290 > Shutting down device 31 20:55:00.290 > All devices shut down. 20:55:00.290 > Shutdown handler called 20:55:00.290 > fnTaskManager::~fnTaskManager 20:55:00.290 > ### NetSIO stopped ### 20:55:00.290 > FileHandlerLocal::close 20:55:00.290 > delete FileHandlerLocal 20:55:00.290 > Stopping web service -SteveS use ./run-fujinet 1 Quote Link to comment Share on other sites More sharing options...
a8isa1 Posted November 26, 2021 Share Posted November 26, 2021 12 minutes ago, tschak909 said: use ./run-fujinet ah working now Thanks Thom (and apc, of course)! -SteveS 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted December 19, 2021 Share Posted December 19, 2021 Is this possible to be compiled to run on Windows XP? 3 Quote Link to comment Share on other sites More sharing options...
+DjayBee Posted December 19, 2021 Share Posted December 19, 2021 3 hours ago, Kyle22 said: Is this possible to be compiled to run on Windows XP? Best failed joke ever. ? 3 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted December 19, 2021 Author Share Posted December 19, 2021 15 hours ago, Kyle22 said: Is this possible to be compiled to run on Windows XP? Take the code and build it. I do not know how many times I can say this, we can't keep a VM lying around just to build XP binaries. PLEASE STOP ASKING, AND DO IT YOURSELF! -Thom 2 Quote Link to comment Share on other sites More sharing options...
+Stephen Posted December 20, 2021 Share Posted December 20, 2021 Would it be possible to enclose the Fujinet in tin foil instead of making an XP build? 2 Quote Link to comment Share on other sites More sharing options...
+DjayBee Posted December 20, 2021 Share Posted December 20, 2021 7 hours ago, Stephen said: Would it be possible to enclose the Fujinet in tin foil instead of making an XP build? Sounds like a great idea. This would make it less susceptible to WLAN-rays. 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted December 27, 2021 Share Posted December 27, 2021 All I am asking is 'IS IT POSSIBLE?' If so, I will attempt to build it. All I am asking for is a YES on NO. Thanks. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted December 27, 2021 Author Share Posted December 27, 2021 21 minutes ago, Kyle22 said: All I am asking is 'IS IT POSSIBLE?' If so, I will attempt to build it. All I am asking for is a YES on NO. Thanks. You're looking for me, someone who does not have the required toolchain or environment, to see if it's possible? How can I? Try for yourself, and see if it's possible. -Thom 2 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted December 27, 2021 Share Posted December 27, 2021 I will attempt to discover it for myself. If I find a solution, I will release it. Quote Link to comment Share on other sites More sharing options...
apc Posted December 27, 2021 Share Posted December 27, 2021 At the moment FujiNet PC on Windows can be run via a) Linux binary in WSL or b) work in progress Windows native port. For b) the priority is to get it working on 64-bits first. On 12/19/2021 at 4:50 AM, Kyle22 said: Is this possible to be compiled to run on Windows XP? The answer is: most likely not, not yet. If anyone would like to experiment and/or to contribute, use "mingw" branch from repo https://github.com/FujiNetWIFI/fujinet-pc.git Check https://github.com/FujiNetWIFI/fujinet-pc/blob/mingw/Windows.md for instructions. Jan 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.