Jump to content

Talk:X68000

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

picture

[edit]

Someone add picture, please?

Visual Shell

[edit]

My edit has been reverted due to NPOB. I'm sure that the initial GUI system of X68000 is called ビジュアルシェル (Visual Shell) rather than VS in Japan, however it got doubut that it's an original research. Unfortunately, over ten years ago, I've thrown away that my two X68000s, manuals, Oh! Xs, games and so on, so I can no longer provide any evidences. Can anyone bear and recover my edit? --Uiweo (talk) 10:59, 18 December 2007 (UTC)[reply]

Older model (than SUPER/SUPER-HD) had VS.x GUI. And VS called ビジュアルシェル(Visual Shell) at the operation manual, and many publishment in Japan called VS as "Visual Shell". For example, "X68000活用研究"(X68000 katuyou kenkyu;X68KK) had published in 1987, from Dempa Shinbunsha(means "Radio Newspaper"). Headline of X68KK is available from http://www3.ocn.ne.jp/~kikux68k/x68kbk01.html --Lemmingdead (talk) 08:43, 5 October 2008 (UTC)[reply]
Thanks, Lemmingdead. I have seen your edit belatedly and appreciate your help. --Uiweo (talk) 15:54, 11 November 2008 (UTC)[reply]

Stereoscopic 3D

[edit]

Amongst the specs there's an intriguing mention of a "Stereo scope/3D goggles port". Did any games use this? I assume, based on the tiny amount of information present on the internet, it was a way of controlling a set of those 3D LCD goggles the two eyepieces blank out rapidly in sequence, but I can find almost nothing about them, or any pictures of the goggles. It sounds like the kind of port that was never used. -Ashley Pomeroy (talk) 21:28, 21 June 2009 (UTC)[reply]

Price?

[edit]

How much was a X68000 compared to a NES/SNES/Genesis? --IronMaidenRocks (talk) 17:22, 11 April 2012 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified 2 external links on X68000. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 13:35, 21 July 2016 (UTC)[reply]

Documentation of the Human68K 18.3-long filename FAT format?

[edit]

I would like to read more (that is, an exact byte level description of the used structure) about the internal format of directory entries in the 18.3 FAT variant used by Human68K, and any other logical differences from standard FAT, so that it would become possible to add support for it in third-party drivers or at least let FAT driver implementations cope with the format more smoothly when they would run into it. Is this documented somewhere? (The info might be incorporated into here, into the long filename or even into the Design of the FAT file system article.) --Matthiaspaul (talk) 16:51, 3 January 2022 (UTC)[reply]

Keyboard and mouse

[edit]

What kind of connectors / protocols where used for the keyboard and mice? Were they included with the computer? Pictures would be very useful. 2A02:168:F609:1:284F:5687:CC7:7DF7 (talk) 21:35, 24 January 2024 (UTC)[reply]