Hi! BjÇrn,
On Thu, 25 Oct 12, you wrote to me:
PQ>> Oooh, a game even! (I didn't get that far at all but I ran-up
PQ>> the RR help file, just to see what it was...)
BF> Hey! You can run the EXE on any Windows install. It will be a
BF> small square that'll require glasses to see, but never-the-less.
Oh, I didn't say that the thought of it reminded me of an old nightmare.
Back
in the early 90s at work, we had a copy of OS/2 v2.xx to play with. That's
what we were doing with it, just playing. It had a kitten chasing the
(mouse)
cursor game on it, which seemed fairly innocuous. However a couple of
blokes,
just for laughs, used to delight in leaving the game in a full-screen
situation that, to the unfamiliar, left the PC in such a condition as to
require a power off/on cycle. Well, lo and behold, the friggin' game came
up
full-screen again... every reboot (an OS/2 'feature' that ensured that the
last-run program would again re-run on boot). So, the only solution (it
seemed) was a re-install. For them blokes, this was even better
fun/entertainment than the game itself: see Paul swear flaming oaths, and
re-install OS/2.
PQ>> it choked on disk #2
BF> Strange. No clue as to why?
It was a required reboot to start the GUI setup. Twice, that is two times,
the reboot code didn't work. Even a manual reboot produced the 'kangaroo in
the headlights' stare from DOS, after the reboot... twice. Of course,
running
the GUI setup.exe manually produced the usual "you can't run the setup from
here" (or words to that effect) abuse that is so typical of M$ errors
screens.
PQ>> Thanks again. It was 'interesting' for 45 minutes.
BF> There's no giving up that easily!
It was intense! :)
BF> But I think we need a special WFW311 echo to continue this
BF> interesting discussion. It rather is kinda OT in here...
Agreed. [EOT]
Cheers,
Paul.
... Therapy helps, but screaming obscenities is cheaper.
--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
|
