9/4/2023 0 Comments Wormsnet hostbuddy![]() ![]() Old W:A versions started getting an error message when connecting to WormNET, due to connecting to WormNET by its IP address which was about to change. The WormNET statistics page was announced. JA memory corruption bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging. JWormNET server was inaccessible for a few hours due to migration to another ISP. JThe Team17 network was down while Team17 copied a file. AugTeam17 DNS servers were down for more than a few hours. August 10–11, 2009 Planned outage due to network maintenance. August 23–24, 2009 Another DNS outage that lasted a good part of the weekend. The problem causing random DNS outages is believed to have been fixed on the 25th. Septem(marked by a red line) WebSnooper began logging activity in all WormNET channels. SeptemA large number of schemes have been added to HostingBuddy. September 22–23, 2009 WormNAT2 server went down for 16 hours due to broken link dependencies. December 17–18, 2009 Several WormNET outages which left the bots outside the channels for a while. February 9–10, 2010 A WormNET restart left the bots outside the channels for a while. MaThe logging bot failed to rejoin the channels due to an unknown reason. March 17–18, 2010 Bug in bot timeout code caused the logging bot to remain disconnected from WormNET for over a day. Ma(later) Temporary Team17 network outage. ![]() April 24–25, 2010 WormNET server was down for the weekend. The server hosting the WormNET bots was down for most of the day. Additionally, a problem in the replacement HostingBuddy instance caused a large number of bogus (unjoinable) games to be hosted. JA problem in HostingBuddy caused a large number of bogus (unjoinable) games to be hosted. October 10–12, 2010 WormNET server nearly unusable due to considerable network lag (caused by problems at Team17's ISP). November 28 – December 5 HostingBuddy maintenance. JanuHostingBuddy dropped support for 3.6.28.0 users.ĭecemHostingBuddy began warning 3.6.28.0 users of upcoming end of 3.6.28.0 support. FebruHostingBuddy's memory corruption problem was fixed. MaUsers of W:A versions older than 3.6.31.0 start seeing a warning screen when connecting to WormNET. ApW:A versions older than 3.6.31.0 can no longer connect to WormNET. AugTemporary WormNET outage due to problems from Team17's ISP. Download VirtualHostXĮxisting users may download the most recent versions of VirtualHostX.Įxisting users may download the most recent versions of Hostbuddy.Įxisting users may download the most recent version of Hobo.April 10–11, 2012 WormNET outage due to server failure. It’s been a privilege helping you get work done. Many of you have been customers for well over a decade. Thanks to everyone for your support of VirtualHostX throughout the years. With VirtualHostX being sunset, sales of its sibling apps, Hostbuddy and Hobo, are ending, too. ![]() Your existing license for VirtualHostX will continue working indefinitely. No need to purchase additional seats.Īlong with the above, VirtualHostX will continue to be available for download.Īs of February 1, 2022, all auto-renewing subscriptions will be stopped and you will not be billed again. If you have a license for VHX, feel free to install it on as many Macs as you want. Activation limits for existing customers have been removed. Support for future versions of macOS is not guaranteed.Ħ. Bug fixes will be shipped as necessary.Ĥ. Your copy of VirtualHostX will continue working on Intel-based Macs.ģ. What happens next, and what does this mean for customers?ġ. As of November 24, 2021, I’m announcing that VirtualHostX is sunset as an actively developed product. None of those paths forward are tenable for many different reasons. Options included rebuilding VHX on top of Docker, requiring customers to pay for a third-party virtualization app such as Parallels or VMWare, or building my own virtual machine layer on top of Apple’s system frameworks. I’ve spent the better part of the last year and a half investigating ways to bring VHX to Apple’s new machines. If you’ve been paying attention, you’ve noticed that VirtualHostX is not compatible with Apple Silicon Macs. In June 2020, Apple announced their transition to M1 Macs – powered by their own CPUs, which began shipping later that year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |