Impressive , checking the latest version , thanks for the update
With latest version of WebOne and update of Escargot, now all versions of MSN Messenger (1.0 - 2009) are working on all OSes. Previously there were problems with version 4.7 and up on Windows 9x/2000 and pre-SP3 XP. Now, all are working. So it's now possible to run MSN Messenger 5.0-7.0 under Windows 98 and successfully connect it to Escargot network. As well as "classic" Messenger 4.6.
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Hey all can someone help me out here? Im using 86box, got a dos622/wfwg 3.11 VM setup with npcap without problems with IE 5 16bit installed also got latest WebOne installed on my host Windows 11 machine running and reporting no issues, but even with port 8080 open and my gateway showing the VM connected to the network I cant try to connect the VM to webone i imagine its something im' misunderstanding in how to configure IE 5's proxy settings could someone please give me a bit of a break down to go step-step?
EDIT: or for that matter oprea 3.62?
I think you have problems at 86Box configuration. It have very strange networking stack, and it's not easy to connect from an 86Box to host PC. Consider use something like VirtualBox or Microsoft Virtual PC 2007, they are better at network level (IMHO).
First, try any of ways to get 86box connected to host PC: https://86box.readthedocs.io/en/latest/hardware/network.html
Then try to ping the host OS from 86box. If it's success, probably WebOne will be accessible by that IP address, and port 8080. Set them in browser settings (does not matter, MSIE, Opera, or other).
An other way is to set 86Box to SLIRP mode, verify that WWW is correctly pinging, then launch WebOne on a some public location (such as a rented VPS server) and use it. This is only way that doesn't rely on 86box local networking problems.
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
rarcher wrote on 2024-05-29, 20:54:IE 5 16bit
Tried 86box again. And now I have got success with it.
First, tried with Win98 guest OS. Found that it's not possible to made LAN working with NE2000 emulated NIC. Switched to RTL8029AS, all became ok. Seems that there's a bug in 86box (v3.11, haven't tested something newer). And...it's really possible to have a working connection to host PC from an 86box virtual machine. Good news. 😀 Okay, going to WfW 3.11...
rarcher wrote on 2024-05-29, 20:54:step-step
1. - Install NPCAP in WinPcap-compatible mode (it will ask for the mode during installation). Then open Device Manager (at host OS), and manually install a "legacy device" called "Microsoft KM-TEST Loopback Adapter". The driver is bundled with Windows installation.
2. - Open Network and Sharing Center and configure the KM-Test adapter to use static IP address 192.168.0.1, mask 255.255.255.0. Later this IP will be the IP address of proxy server on host machine.
3. - Go to 86box and set up an configuration with virtualized Realtek RTL8029AS adapter, connected to PCap->Microsoft KM-TEST.
4. - Install MS-DOS, then WfW 3.11 with correct SVGA and RTL8029AS drivers.
5. - Install Microsoft TCP/IP-32 for Windows For Workgroups 3.11, it's called "tcp32b.exe" at FTPs. Older, just "Microsoft TCP/IP for Windows For Workgroups 3.11" (16-bit) is incompatible.
6. - Set IP address to 192.168.0.11 ("11" may be any number in range 2-254), subnet mask 255.255.255.0.
7. - Install MSIE 5.0 16-bit and "se128-16.exe" High Encryption Patch.
8. - Configure MSIE to use "Local area network or another dialer", not MSIE's dialer. And also to use automatic configuration URL "http://192.168.0.1:8080/auto.pac".
9. - Run both WebOne and MSIE, and have a nice experience of browsing WWW via 16-bit browser. 😀
Steps for Opera 3.62, Netscape Navigator are similar.
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.17.1 is ready.
It's a minor update, containing mostly bug fixes and configuration update.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.1
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.17.2 is ready.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.2
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Awesome ATauenis!
Just tested the latest version with (for the moment) a Windows 98 VM using Firefox 2.0, and it works great.
I copied the CA cert file over to the Windows 98 and imported it, and it seems I'm not getting any more messages with "trusting issues" 😀
Keep up the good work!
Be free!
Thanks.
---
Version 0.17.3 is ready.
There are many bugs were fixed, and it contains a bit updated Retro Online Video Player.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.3
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.17.4 is ready.
There are some bugs fixed in it. Thanks to anyone who reporting bugs via GitHub and other ways, and who contributed media player support improvement code.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.4
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.17.5 is ready.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.5
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.17.6 is ready.
Download page: https://github.com/atauenis/webone/releases/tag/v0.17.6
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Version 0.18.0 is ready.
Download page: https://github.com/atauenis/webone/releases/tag/v0.18.0
2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.
Now using .NET 8.0 Runtime instead of .NET 6.0. ... Windows 7 (2008 R2) is no longer supported
Здравствуйте ATauenis,
as you probably know, most people who use old browsers are using old operating systems. Using an old browser is - in most cases - no benefit compared to using a newer version. We just use it, because the new versions don't run on old operating systems. So your main audience are people using old operating systems.
Since we need a modern operating system for your solution, it makes more sense directly using a modern browser on the modern operating system. With WebOne we need 2 machines running at the same time: One that is compatible with WebOne and one that the user actually likes to use.
With your current solution you are drasticly limiting your audience: You are addressing people who like old operating systems, but who are using a modern operating system to get the old operating system working.
Are you able to reduce the system requirements of WebOne so we can also use it directly on old operating systems instead of your current path: reducing the compatibility of WebOne step by step so it works on less and less operating systems where it is actually needed.
My fear is, that when you started with dot net 6 years ago, it was a one way ticket with no return. The dot net framework is pretty incompatible with old operating systems. So becoming compatible with old systems will be quite a challenge for you.
Start me up wrote on Today, 03:48:Здравствуйте ATauenis, as you probably know, most people who use old browsers are using old operating systems. Using an old brow […]
Now using .NET 8.0 Runtime instead of .NET 6.0. ... Windows 7 (2008 R2) is no longer supported
Здравствуйте ATauenis,
as you probably know, most people who use old browsers are using old operating systems. Using an old browser is in most cases no benefit compared to using a newer version. We just use it, because the new versions don't run on old operating systems. So your main audience are people using old operating systems.Since we need a modern operating system for your solution, it makes more sense directly using a modern browser on the modern operating system. With WebOne we need 2 machines running at the same time.
With your current solution you are drasticly limiting your audience: You are addressing people who like old operating systems, but who are using modern operating systems to get the old operating system working.
Are you able to reduce the system requirements of WebOne so we can also use it on old operating systems instead of your current path: reducing the compatibility of WebOne step by step so it works on less and less operating systems where it is actually needed.
Sadly I don't think the system requirements can be reduced, as this requirement comes from .NET 8.0 itself. Don't know if self-contained releases can be made work with Win7/2008 R2, however.
The fact that it's unlikely for .NET 8.0 to support Win7/2008 R2 was one of the reason I still mainly target .NET 6.0 even though it has become EOL, and haven't made the switch to .NET 8.0 (or even 9.0) yet.
In fact, even .NET 6.0 normally required some ESU stuffs to work properly with Win7/2008 R2, and published .NET 6.0 projects in self-contained form did not work correctly on Win7/2008 R2 when it just came out. The related issues were fixed after a later VS2022 release so for now it's possible to publish .NET 6.0 projects self-contained and run on Win7/2008 R2, but I cannot expect the same for .NET 8.0 since Win7/2008 R2 has gone past ESU support date when it's released.
An alternative would be using some computer boards such as Raspberry Pi as a dedicated WebOne server, as modern .NET versions support Linux and ARM very well.
My fear is, that when you started with dot net 6 years ago, it was a one way ticket with no return. The dot net framework is pretty incompatible with old operating systems. So becoming compatible with old systems will be quite a challenge for you.
Sadly I don't think the system requirements can be reduced, as this requirement comes from .NET 8.0 itself.
Well, let's not ignore the elephant in the room: To break the chains by abandoning the dot incompatibility framework.
Start me up wrote on Today, 05:16:My fear is, that when you started with dot net 6 years ago, it was a one way ticket with no return. The dot net framework is pretty incompatible with old operating systems. So becoming compatible with old systems will be quite a challenge for you.
Sadly I don't think the system requirements can be reduced, as this requirement comes from .NET 8.0 itself.
Well, let's not ignore the elephant in the room: To break the chains by abandoning the dot incompatibility framework.
When I said about using a Linux-powered computer board as a dedicated WebOne server, that's how I've been using it.
Though I haven't really maintained its WebOne installation for a while. The board currently runs Ubuntu 20.04, which should still be able to use the latest version. (EDIT: Just updated it. Looks good here.)
As for compatibility, I think modern .NET (not Framework) supported Linux much better than Windows, since portable (distro-generic) releases are simply limited by libc (glibc/musl) version. So unless you're running a distro with too old libc, .NET should run fine.
A caveat would be that .NET usually requires the libicu library by default, which may not be available on some environments, and it's usually packaged in the "icu" package among distros. It's possible to still run the program in this case by disabling Globalization using an environment variable, provided the program itself doesn't make use of Globalization stuffs.
PS: .NET projects published in self-contained format will not require .NET runtime installed on the target environment. For Linux, such program should be able to run out-of-box if the system's libc meets requirements, as well as having libicu installed.
@Start me up, please keep your reverse-fanboy'ism to yourself.
It is very reasonable to be on .NET 8.0 right now and do the jump to .NET 10 in not-so-far future.
This is not the place to support your Win 3.11 as a viable operating system for your server.
"640K ought to be enough for anybody." - And i intend to get every last bit out of it even after loading every damn driver!
A little about software engineering: https://byteaether.github.io/
LSS10999 wrote on Today, 08:56:When I said about using a Linux-powered computer board as a dedicated WebOne server, that's how I've been using it.
So you have the same problem, like I have: You need a second machine to use WebOne.
Start me up wrote on Today, 09:55:So you have the same problem, like I have: You need a second machine to use WebOne.
Yeah, but this "second machine" doesn't have to be a full-fledged PC.
I don't think it's easy to target older OSes directly so as to, like you said, be able to run WebOne on the same machine that would be browsing the web with it.
WebOne needs to handle a lot of complex stuffs that older OSes may not have the necessary APIs/libraries to do so. Some functionalities may require installing other software/libraries which further complicates the compatibility problem.
