8 ms·

You probably only need access to DOS on your Communicator. To achieve this you need to create a file B:\NOKIA\INSTALL.BAT and reboot the communicator. From this

You probably only need access to DOS on your Communicator. To achieve this you need to create a file B:\NOKIA\INSTALL.BAT and reboot the communicator. From this batch file you can call Nokolisp. If "INSTALL.BAT" exits the normal GEOS shell will start.

alexshendi 2y ago
More details on: http://win98.altervista.org/9110/dos9k/aboutdos.html http://win98.altervista.org/9110/dos9k/aboutdos.html
lproven 2y ago
Oh no. That would be trivially easy and thus unworthy of hacker folklore. :-) It was much more complicated and much more impressive than that: https://news.ycombinator.com/item?id=20019399 https://news.ycombinator.com/item?id=20019399
- lproven 2y ago
  You can glean a little more of the history from this long and involved Reddit thread. https://old.reddit.com/r/bestof/comments/1umqu6/timonoko_accidentally_makes_a_lispbased_os_for_a/ https://old.reddit.com/r/bestof/comments/1umqu6/timonoko_acc... It's hard because you have to work around @timonoko's missing comments, but it's intringuing.
- alexshendi 2y ago
  Maybe you'd be interested in this: https://github.com/timonoko/Nokolisp_On_Nokia_phone https://github.com/timonoko/Nokolisp_On_Nokia_phone But I can't figure out how to install it, while I know how to build nokolisp with MASM. Thus the MSDOS based Nokolisp is more useful, at least for me. BTW the cited HN posting contains at least one factual error: The Nokia Communicator 9110 was based on an 486SX SOC, not an 80186. But to each his own.
  - timonoko 2y ago
    It looks like nokia.exe is somekind of special version of noko.exe. For example it refers to B:/NOKIA/COMMAND.COM instead of MSDOS-standard C:/COMMAND.COM.
    - lproven 2y ago
      Oh my word! Is this your project, then?
      - timonoko 2y ago
        Not much of a project... I think nokia.exe is just made by modifying it while running it and freezing the situation with (make-exe). Not a good practice, imho.

alexshendi 2y ago

More details on: http://win98.altervista.org/9110/dos9k/aboutdos.html http://win98.altervista.org/9110/dos9k/aboutdos.html

lproven 2y ago

Oh no. That would be trivially easy and thus unworthy of hacker folklore. :-) It was much more complicated and much more impressive than that: https://news.ycombinator.com/item?id=20019399 https://news.ycombinator.com/item?id=20019399

lproven 2y ago
You can glean a little more of the history from this long and involved Reddit thread. https://old.reddit.com/r/bestof/comments/1umqu6/timonoko_accidentally_makes_a_lispbased_os_for_a/ https://old.reddit.com/r/bestof/comments/1umqu6/timonoko_acc... It's hard because you have to work around @timonoko's missing comments, but it's intringuing.
alexshendi 2y ago
Maybe you'd be interested in this: https://github.com/timonoko/Nokolisp_On_Nokia_phone https://github.com/timonoko/Nokolisp_On_Nokia_phone But I can't figure out how to install it, while I know how to build nokolisp with MASM. Thus the MSDOS based Nokolisp is more useful, at least for me. BTW the cited HN posting contains at least one factual error: The Nokia Communicator 9110 was based on an 486SX SOC, not an 80186. But to each his own.
- timonoko 2y ago
  It looks like nokia.exe is somekind of special version of noko.exe. For example it refers to B:/NOKIA/COMMAND.COM instead of MSDOS-standard C:/COMMAND.COM.
  - lproven 2y ago
    Oh my word! Is this your project, then?
    - timonoko 2y ago
      Not much of a project... I think nokia.exe is just made by modifying it while running it and freezing the situation with (make-exe). Not a good practice, imho.