MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr) (08/06/90)
Beside the problems of dictating new standards to memory management via
the himem.sys driver supplied with Windows 3.0 by MS, which has the
effect, that after return from a "well-behaving" program like Windows 3.0,
older programs cannot use extended memory anymore, are there any experiences
of how to start ST V/286 from within Windows in standard/386-mode AND retur-
ning to Windows by task-switching? Even better: Did anybody manage to run
ST in a Windows-window? If nothing works: Will there be a DigiTalk-ST
running under Windows 3.0 ?
Lots of questions, I know....
Thanks in advance -
Thomas
-------
Thomas Muhr, Technical University of Berlin, BITNET: muhrth@db0tui11
Project ATLAS - Computer Based Tools for Qualitative Research
"Computers, like every technology, are a vehicle
for the transformation of tradition." (WINOGRAD/FLORES)CHRIS_LAVENDER_WADE@cup.portal.com (08/07/90)
Smalltalk V under Windows available December. Smalltalk 80 under Windows (ver 2.5) available now.
KRW1@Lehigh (08/07/90)
Digitalk's successor to Smalltalk/V 286 will be Windows based. It is expected by the end of the year. It will also include a graphical application design facility and will generate exe files. (This info comes from discussions with Digitalk representatives on CompuServe and BIX).
ergo@netcom.UUCP (Isaac Rabinovitch) (08/08/90)
In <90218.105603MUHRTH@DB0TUI11.BITNET> MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr) writes: >Beside the problems of dictating new standards to memory management via >the himem.sys driver supplied with Windows 3.0 by MS, which has the >effect, that after return from a "well-behaving" program like Windows 3.0, >older programs cannot use extended memory anymore, are there any experiences >of how to start ST V/286 from within Windows in standard/386-mode AND retur- >ning to Windows by task-switching? Even better: Did anybody manage to run >ST in a Windows-window? If nothing works: Will there be a DigiTalk-ST >running under Windows 3.0 ? I've never used Windows, and I'm not even much of a Smalltalker, but I suggest you forget about ST V/286 and Windows, at least for now. In my experience, you don't want *anything* running with ST V/286. It seems to hang if I run any interactive TSRs at the same time. I'm not sure if it'll get along with any extended memory managers, but since it manages extended memory itself, that's moot. My worst experience in this department: I have a quite well-behaved screen blanker that I'm sure cannot (at least by itself) destroy a Hercules monitor. But when I made the mistake of running it with with ST V/286, it waited the requisite 10 minutes and blanked my screen *forever*. I suppose ST V/286 must interact with the video constantly, and two entities trying to reprogram a Hercules card at the same time is guaranteed to result in tragedy! I *always* reboot before running Smalltalk V/286, and I suggest you do the same! -- ergo@netcom.uucp Isaac Rabinovitch atina!pyramid!apple!netcom!ergo Silicon Valley, CA uunet!mimsy!ames!claris!netcom!ergo "I hate quotations. Tell me what you know!" -- Ralph Waldo Emerson
nbladt@aut.UUCP (Norbert Bladt) (08/08/90)
MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr) writes: >Beside the problems of dictating new standards to memory management via >the himem.sys driver supplied with Windows 3.0 by MS, which has the >effect, that after return from a "well-behaving" program like Windows 3.0, >older programs cannot use extended memory anymore, are there any experiences >of how to start ST V/286 from within Windows in standard/386-mode AND retur- >ning to Windows by task-switching? Even better: Did anybody manage to run >ST in a Windows-window? If nothing works: Will there be a DigiTalk-ST >running under Windows 3.0 ? >Lots of questions, I know.... >Thanks in advance - >Thomas Without even trying this kind of things I would expect that Smalltalk V/286 will not work if the system is already in protected mode. Perhaps if you run Win3.0 in real mode that could work. I have not tried it. I don't have the 3 or 4 MBytes needed for Win 3.0 and no 386 or 486 yet. We had similar experiences with the older WIN386 and the 386Max program. WIN386 would not start because the 386 was already in protected mode. BTW You start WIN3.0 in real mode with the option /r. Hope this helps you running WIN3.0 in real mode and ST/V. Regards, Norbert. -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 52 92 14 EMail: ..!uunet!mcsun!chx400!hslrswi!aut!nbladt -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 52 92 14 EMail: ..!uunet!mcsun!chx400!hslrswi!aut!nbladt