jetsetdanny

Thank you for this release, Andy! 👍 I certainly will (using Rollback), but it will probably have to wait until its turn comes for a 'proper' recording of mine to be placed on JSW Central with a video on the JSW Central YouTube channel. I am short of spare time nowadays and proceed with my JSW activities according to a plan I have. I look forward to playing "JSW - 2024" whenever its time comes, though 🙂 .

Thank you for every visit you pay to the JSW Central YouTube channel! 😁 And for coding "Manic Miner 2" in Scratch! 🙂

You've got a brilliant son!!! 😁

"Willy Meets The Beatles" is a 2012 JSW game by Simon D. Lee (TechnicianSi), with music created by Paolo Arus (DarkHorace). This excellent tribute to the legendary band of the 1960s was originally released in January 2012, in TZX and Z80 format, followed by a bug-fixed revision in April 2012. Unfortunately, the last officially released bug-fixed revision still contained one critical bug that went unnoticed for over a decade, even though an RZX recording of the game was published by Pavel Plíva (Pavero) on the RZX Archive immediately after the revision's release (incidentally, this recording features an unnecessary loss of life in "Candlestick Park" [28]). The issue occurred with the right exit from the room "End of an Era" (59), where the toilet run begins. This exit was mistakenly set to loop back to the same room. As a result, during the toilet run, Willy would repeatedly re-enter the room on the left after exiting on the right, instead of proceeding to the intended final room, "Free as a Bird" (60). This room was clearly meant to serve as the ending, as evidenced by its content — "The End" and "Thank You For Playing" — and by Simon's comment on WoS, where he referred to "Free as a Bird" as "the final screen". I discovered this problem after completing the game and recording an RZX walkthrough for my JSW Central YouTube channel. When I worked on updating the information on the game's page on JSW Central, I suddenly realised Pavel's recording didn't show the correct ending, and then I realised that the last officially released revision of the game had the right-exit-in-Room-59 problem. I have corrected it (by modifying the value at address #ECEA in Memory Bank 6 from #3B to #3C, thus setting the right exit from "End of an Era" to "Free as a Bird") and prepared a bug-fixed version of the game in TZX and Z80 format (both are the original release formats). The fixed version can be downloaded from "Willy Meets The Beatles" page on JSW Central. I also re-recorded the game and made a video of it, which you can see on the JSW Central YouTube channel. I would strongly encourage everyone to play the game, especially if you are fond of The Beatles. It's quite easy in terms of gameplay. It really sticks to the theme and it features excellent music ("Back in the USSR" on the title screen and "Lady Madonna" as the in-game tune), played using SoundTracker. It was the first JSW64 game to utilise this solution. In fact, the game's development inspired John Elliott to release version 2.3.5 of JSWED, which introduced the option to replace Ian Collier's default JSW64 music player with the SoundTracker player by BZYK (Piotr Baczkiewicz).

Thank you! 🙏

@Atharv95 - is that you, Jet Set Willie? Did you register another account to solve the problems related to getting logged out or something?

This is what ChatGPT had to say about it: My question: The message "Illegal memory address" in Blitz Runtime Window (trying to run an older piece of software on a modern Windows 11 laptop) - what does it mean and how can it be remedied? ChatGPT's reply: The message "Illegal memory address" in the Blitz Runtime Window indicates that the software attempted to access a memory location that it doesn't have permission to use or doesn't exist. This is a common issue with older software that wasn't designed for modern operating systems like Windows 11. Here’s how you can troubleshoot and potentially fix it: 1. Run the Program in Compatibility Mode Older software may not work correctly on modern systems due to differences in system architecture. Try running the program in compatibility mode: Right-click the program's executable (.exe) file. Select Properties. Go to the Compatibility tab. Check Run this program in compatibility mode for: and choose an older Windows version (e.g., Windows XP or Windows 7). Also, check Run this program as an administrator for additional permissions. 2. Enable 32-bit Compatibility If the program is 32-bit and you're using a 64-bit system, it might have trouble running properly. Windows 11 still supports 32-bit applications, but you might need to ensure compatibility: Check if your system has WOW64 (Windows-on-Windows 64-bit) enabled. This is typically on by default but can be re-enabled in Windows Features if needed. 3. Check for Dependencies Older programs sometimes rely on specific libraries or runtime environments. The following may be necessary: Install DirectX 9: Some older programs rely on this version. Install older Microsoft Visual C++ Redistributable packages. Install .NET Framework 3.5 (enable it through "Windows Features"). 4. Use a Virtual Machine or Emulator For software deeply tied to older systems, running it in a virtual machine (VM) with an older OS might work better: Install software like VirtualBox or VMware Player. Set up a VM running an older Windows OS (e.g., Windows XP or Windows 7). Run your program inside the VM. Alternatively, try DOSBox or similar emulation software if the program is from an even older era. 5. Disable Modern Hardware Features Temporarily Some Blitz-based applications expect older hardware configurations: Disable hyper-threading or adjust processor affinity: Open Task Manager. Right-click the program under the "Processes" tab. Choose Go to Details, then right-click and set Processor Affinity to a single core. Lower graphics acceleration: Go to Display Settings > Advanced Display Settings > Troubleshoot (if available). 6. Patch or Update the Program Check if there's a patched or updated version of the program. Sometimes, developers or the community release updated builds for older software. 7. Debugging in Blitz (Optional) If you have access to the Blitz source code or debugger, check the following: Ensure the program isn't trying to access null pointers or unallocated memory. Check for compatibility with modern file paths (e.g., long paths or special characters). Let me know how it goes or if you need help with any of these steps! 😊 End of ChatGPT's reply. Was it helpful to any extent?

Thank you so much for this detailed explanation of your further work on the code, Norman Sword! The modifications you've added sound most impressive, and definitely like something that would merit public release. 🙂 So is there any chance that after the Spider version updates have stopped on December 31st (2024, I take it), a new 4.00 version will be released in 2025? In any case, I understand that there will be no more official releases of v. 3 (v. 3.01 being the last one), so the situation is clear as far as my RZX-recording and movie-making plans are concerned (I will publish a walkthrough of v. 3.01 in December 2024 if all goes well). So thank you for clarifying the situation! 👍

I am planning to play, RZX-record and make a video of v. 2 and v. 3 of "Manic Jet Set Willy" in the near future (December). I understand that v. 3.01 was the last one released. A kind request to Norman Sword: could you please confirm that no more versions will be forthcoming or let us know if you should happen to have any newer versions and plan to release them (is so, when?).

Thank you for this contribution, playingwithwilly! 👍 Craig Rothwell's version has been discussed twice already on this forum. There is a separate topic dedicated to it: Plus it was discussed in this thread, starting here. The discussion includes the link to Craig's archived page with the cheat code. Andy, would you be able to move the posts from this thread to this one to avoid a duplication of topics? I've just tried doing it, but I'm not quite sure how to do it and wouldn't want to mess things up.

Have you visited the Happy Tulip Lounge or the Pleasant Coctail Bar yet, Mr Badiels? 😉

I would suggest playing with some "assistive tools", such as RZX-recording the game and using the Rollback feature (my personal preference) or saving and loading snapshots. I always use Rollback when I play JSW and MM games these days. I know, it's cheating, but I would consider it a waste of time to play a game in a different way. And some of the games designed in recent years and decades are so forbiddingly difficult that they are *meant* to be played with assistance. Using Rollback changes the perception of difficulty level enormously. I am often astonished when people complain about (some really relatively easy - I'm not referring to "What a Wonderful World of Willie" here) games being difficult. They're not if you can roll back after each mistake and try again. It's just that you have to be using the proper tools 🙂 .

It probably won't be much help, but, for the record, the roof in my "Willy's New Mansion" look like this: - In the original edition: have a look here starting at about 36:50; - In the Special Edition: have a look here starting at about 55:59. Oh, and "The Temple" looks really cool! 👍 Could you tell us more about the game you are creating? 🙂

I like it 🙂.

It does. A number of games are only toilet-completable thanks to this feature.