MiSTer FPGA Forum

Neohabitat is a relaunch of the first MMO, Lucasfilm's Habitat. MiSTer did seem capable of logging in, as seen in a youtube video from 2019. I've been trying for weeks and the closest I've gotten is with these steps:

1. Set system modem to 1200 baud.
2. Save settings and reset core.
3. Check whether settings are still correct, set C64 UART to RS232.
4. Insert and load Habitat floppy disk 1
5. Press F7 for Terminal
6. Enter at
7. Enter atdthabitat.themade.org:1986
8. Press F12 for OSD menu and set C64 UART to joystick
   (Modem dial-in tones can be heard)
9. Set C64 UART back to RS232
10. Press ESC to exit Terminal
11. Enter user name and press Enter
12. When Habitat prompts you to press "ALT-N", press F12 into the OSD and insert the second side of the disk
13. Exit OSD and simply press a button
14. Neohabitat is loading
    (it stays on the lucasfilm's screen and you never spawn)

I've been using only standard and jiffydos roms.

While I havent personally done it with the mister or a real c64 here are some specific instructions for an actual c64 you can check if you are doing the right steps .. https://github.com/frandallfarmer/neoha ... RealC64.md

No matter how many configurations and attempts I tried, I couldn't "dial out" from within Habitat.
I can dial out with CCGMS, but once you reset, the connection is also reset.
So, I finally got it working but it requires the use of the original C64 Term program from Commodore.
You can find it here first on list...

Just like with your setup:

1. UART set to Modem, 1200 Baud

2. Hardware->Expansion = RS232

3. Hardware->RS232 Mode = UP9600

Then I did:

1. Mount the C64 Term Disk and Load "*",8,1 then Run

2. Once in the Term, you'll be typing gibberish.... Hit F4 for the Menu

3. In the Menu, hit B, select 1200 and press Enter then press T to return to the terminal

4. type in at

5. then atdthabitat.themade.org:1986

6. once it dials out and tells you it connected with 1200 Baud, Press F4 again for the Menu

7. Press E to Exit Back to Basic

8. Swap in the Habitat Disk 1 and Load it up

9. Enter your Name to use and press enter

10. At the "ALT-N" prompt, swap in the 2nd disk via OSD and hit any key

11. Give it some time...music will stop after a little bit and you'll think it crashed...it didn't....wait a while and it will start back up and eventually get into the game

Hope you can reproduce it and it helps.
On a side note, if you can actually dial out from within Habitat (you hear the dial tone) then you can try your steps again but without switching from RS232 to Joystick...keep it at RS232

@Flandango When I boot up Habitat disk 1 and enter my name then F7 to enter the Terminal screen and type atdthabitat.themade.org:1986 (might have to do it a few times). I don't hear the dial out until I continue disk one load. A long time ago I would hear the dial out from the Terminal window.
Then when it't time to load disk #2 it never seems to finish loading.

@Flandango I'll try your process when I get home.

Flandango wrote: ↑Fri Mar 29, 2024 4:38 pm

No matter how many configurations and attempts I tried, I couldn't "dial out" from within Habitat.
I can dial out with CCGMS, but once you reset, the connection is also reset.
So, I finally got it working but it requires the use of the original C64 Term program from Commodore.
You can find it here first on list...

Just like with your setup:

1. UART set to Modem, 1200 Baud

2. Hardware->Expansion = RS232

3. Hardware->RS232 Mode = UP9600

Then I did:

1. Mount the C64 Term Disk and Load "*",8,1 then Run

2. Once in the Term, you'll be typing gibberish.... Hit F4 for the Menu

3. In the Menu, hit B, select 1200 and press Enter then press T to return to the terminal

4. type in at

5. then atdthabitat.themade.org:1986

6. once it dials out and tells you it connected with 1200 Baud, Press F4 again for the Menu

7. Press E to Exit Back to Basic

8. Swap in the Habitat Disk 1 and Load it up

9. Enter your Name to use and press enter

10. At the "ALT-N" prompt, swap in the 2nd disk via OSD and hit any key

11. Give it some time...music will stop after a little bit and you'll think it crashed...it didn't....wait a while and it will start back up and eventually get into the game

Hope you can reproduce it and it helps.
On a side note, if you can actually dial out from within Habitat (you hear the dial tone) then you can try your steps again but without switching from RS232 to Joystick...keep it at RS232

@Flandango Thank you for suggesting dialing out using C64 Term. That worked!!

Ok I think I got it work without needing to use 64_Term...

Settings as before...

1. Bootup Habitat Disk 1

2. Enter Name and press F7 to enter Terminal

3. type in atbaud1200 and press Enter

4. then at&k0 and press Enter (that's a Zero)....you may get an OK response

5. then atdthabitat.themade.org:1986....wait for it dial out before exiting terminal

6. after it dials out and the dial tone/connecting sound effects finish...

7. type at and press enter...you should see Connected at 1200 or something like that.

8. Press ESC to get out of Terminal and press enter to continue...

While entering commands in the Terminal after you get a response back....you may be entering the text over the "response"...but that is ok...at least for me

This process has worked 3 times for me so far.....hope it works for you too

On a side note, I added an entry in /media/fat/linux/MidiLink.DIR for habitat so you don't have to type out that whole atdt command (ex: atdthabitat if your entry is HABITAT)

I can confirm this worked for me. Thank you for the workaround.

Flandango wrote: ↑Fri Mar 29, 2024 8:20 pm

Ok I think I got it work without needing to use 64_Term...

Settings as before...

1. Bootup Habitat Disk 1

2. Enter Name and press F7 to enter Terminal

3. type in atbaud1200 and press Enter

4. then at&k0 and press Enter (that's a Zero)....you may get an OK response

5. then atdthabitat.themade.org:1986....wait for it dial out before exiting terminal

6. after it dials out and the dial tone/connecting sound effects finish...

7. type at and press enter...you should see Connected at 1200 or something like that.

8. Press ESC to get out of Terminal and press enter to continue...

While entering commands in the Terminal after you get a response back....you may be entering the text over the "response"...but that is ok...at least for me

This process has worked 3 times for me so far.....hope it works for you too

On a side note, I added an entry in /media/fat/linux/MidiLink.DIR for habitat so you don't have to type out that whole atdt command (ex: atdthabitat if your entry is HABITAT)

Flandango wrote: ↑Fri Mar 29, 2024 8:20 pm

[*]then at&k0 and press Enter (that's a Zero)....you may get an OK response

Alternately, you can add:

[C64]
TCP_FLOW = 0

to the MidiLink.INI located in /media/fat/linux

bbond007 wrote: ↑Fri Mar 29, 2024 11:48 pm

Alternately, you can add:

Code: Select all

[C64]
TCP_FLOW = 0

to the MidiLink.INI located in /media/fat/linux

Great! I wasn't sure since I didn't happen to notice any other setting being overwritten that way.

Ok! I'm glad it's working for everyone because it gives me hope! Here is as far as I get

Bootup Habitat Disk 1 ✅

Enter Name and press F7 to enter Terminal ✅

type in atbaud1200 and press Enter ✅

then at&k0 and press Enter 

(skip this because I edited midilink.ini C64 "TCP_FLOW = 0")

then atdthabitat.themade.org:1986....wait for it dial out before exiting terminal ✅

after it dials out and the dial tone/connecting sound effects finish... ✅

type at and press enter...you should see Connected at 1200 or something like that. ✅

Press ESC to get out of Terminal and press enter to continue... ✅

after mounting Habitat-B.d64 and pressing a button it seems to load then the "version 1.0" disappears after a while leaving the L U C A S F I L M ' S on screen forever.

here is a link to an attempt from earlier. Someone tell me what I'm messing up: https://youtu.be/5Fh9jdjDb-k

[SOLVED!]

Big thanks to all you wizards! NML32 hooked me up with a hint: disable the parallel port

that fixed it!!!

Yopachi wrote: ↑Sat Mar 30, 2024 1:28 am

[SOLVED!]

Big thanks to all you wizards! NML32 hooked me up with a hint: disable the parallel port

that fixed it!!!

Cool, I'm glad you got it working.