fritchie@acc.stolaf.edu (Scott Fritchie) (02/25/91)
I've been having problems using Windows 3.0 in 386 enhanced mode on a
Compaq 386/20e box with a Thomas Conrad TC4035 token ring network adapter
card in it using NetWare 386. I've spent many hours fiddling with
'setup' and with system.ini without any success. It would be really swell
to get these machines using Windows *and* the Novell network -- perhaps
someone out there can tell me something I've overlooked.
When installing Windows using 'setup', I've been logged onto the network.
Setup recognizes this, telling me I'm using NetWare 286 2.15 or greater or
NetWare 386. Setup proceeds happily. It even searches the network drives
for applications. Setup then finishes doing its stuff without any errors.
I reboot.
Situation 1:
I load ipx (3.01 rev. B) and net3 (3.01 rev. E), then run 'win'. I run
the control panel 'network' program, attach to a file server (it can find
the name of our fileserver, saving me from typing it in), and enter my account
name and password. [Am I supposed to get some sort of confirmation that
the 'attach' has worked? If so, I'm not getting it: the box for the
server/account/password simply disappears after a short wait.]
Then running the file manager I'm told that I have 1 network drive
available, n:, which has 'login' under normal circumstances. Any attempt
to use that drive (file manager, DOS shell, etc.) will lock up Windows. I
can move the mouse, but I can't move a window or icon anywhere. If I press
the left mouse button enough times I can get the machine to beep each time
I do it (filled the event buffer?).
Situation 2:
Just like situation 1, except that I log in before running 'win'. in this
case, the machine hangs at the opening Windows screen. It doesn't get far
enough to switch to text mode to display an error message. A three-finger
salute will clear the screen and then emit a solid, mid-range beep. The
only way to get it to stop beeping is to power the box off.
NOTE: I get the exact same behavior when using netware.drv, vipx.386, and
vnetware.386 from the Supplemental Drivers disk #3, dated 9/20/90, found on
wsmr-simtel20.army.mil/wuarchive.wustl.edu.
As I said, it would be really nice if I could get this to work. I'm
beginning to wonder if this might be a problem with the TCC token ring
card. Any help that anyone could offer would be greatly appreciated.
Following my .sig is more information on the machine's equipment and
what I've been fiddling around with.
-Scott
---
Scott Fritchie, 4810 Underwood Ave., Omaha, NE 68132-2420 USA 402.553.4084
Government Services, American Express's Integrated Marketing Services
Play: fritchie@acc.stolaf.edu ..!umn-cs!stolaf!fritchie Work: 402.498.2124
"Yeah, boss, I'll be in late today. UNIX refuses to boot on my Ford."
Compaq 386/20e with whatever 80MB (?) hard drive it came with, VGA adapter,
Hercules monochrome video adapter, Hitachi IFI-4A CD-ROM interface card
(HITACHIA.SYS driver has not been loaded during my experiments), TCC TC4035
token ring card.
TCC token ring jumpers:
Use primary address 1A20
Slow bus speed
Enable watchdog timer
IRQ 2/9
DMA ch. 5
Large burst speed
IPX:
v3.01 rev. B (900605)
LAN Option: TCC TC4035 v1.00 (900129)
Primary Address (1A20,0A20), IRQ 2/9, DMA 5, ROM D400:0
NET3:
v3.01 rev. E
CONFIG.SYS:
shell = c:\command.com c: /p /e:6000
files = 30
buffers = 10
device = c:\himem.sys
deivce = e:\windows\smartdrv.sys 1024 256
After using the default system.ini 'setup' gave me, I added the following
options because sysini*.txt seemed to say that they were safe. The only
behavior changed was slowing hard disk performance to a crawl.
EMMExclude = A000 - EFFF
AllVMsExclusive = on
DMABufferIn1MB = on
DualDisplay = on
FileSysChange = off
HighFloppyReads = off
InDOSPolling = on
IRQ9Global = on
NetAsynchFallback = on
NetHeapSize = 32
ReflectDosInt2a = on
SystemROMBreakPoint = off
TimerCriticalSection = 3
UniqueDosPSP = on
VirtualHDIRQ = off
-Scott
From tom@mims-iris.waterloo.edu Sun Nov 4 16:11:34 1990
Newsgroups: comp.windows.ms.programmer
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Subject: Frequently Asked Questions (comp.windows.ms.programmer edition)
Summary: version 1.0 [last change: th/90-10-29 --- major overhaul]
Reply-To: tom@mims-iris.waterloo.edu (Tom Haapanen)
Organization: WATMIMS Research Group, University of Waterloo
Date: 29 Oct 90 19:44:35 GMT
TABLE OF CONTENTS
1. Windows newsgroups
2. Windows development tools
3. Windows debuggers
4. Windows extended memory handling
5. Windows screen prints
6. Topics in the comp.windows.ms companion posting
----------------------------------------------------------------------
1. Why are there two newsgroups for windows?
>> comp.windows.ms.programmer is for discussion about developing
Windows software. It is not intended for discussions about
Windows software or for questions about the Foobar SVGA drivers.
comp.windows.ms is for any Windows discussions that do not concern
development of Windows software.
--------------------
2. What tools can I use to develop software for Windows?
>> There are a number of options, which are summarized below:
1. Use the Microsoft Windows SDK (Software Development Kit). This is
a necessity for heavy-duty application development. The SDK is
designed for Microsoft C 5.1/6.0 and Microsoft Macro Assembler 5.1,
but it is possible to use it with other compilers, such as Zortech
C++ (but not including the Borland compilers). If you plan to use
a non-Microsoft compiler, call Microsoft Technical Support to
obtain the free Supplemental Compiler Utilities disk.
2. Use Actor. Actor is an object-oriented programming environment,
with syntax resembling C. It allows quick development of programs
and/or prototypes, and compiles into an "image" file. This must
be distributed along with actor.exe; however, it is possible to
combine these into a single .exe if you have the Whitewater
Resource Toolkit.
3. Use Smalltalk/V. Does anyone know anything about this?
4. Use ToolBook. This is a HyperCard-like development environment
for Windows -- the DayBook demo included with Windows 3.0 is a
ToolBook application. Development work is rapid, but at least
the current versions run very sluggishly, even on 386/25s. There
is a conversion utility available to convert HyperCard stacks
into ToolBook programs.
5. Use W:CASE or WIndowsMAKER, both of which generate C code for
Windows. This will still require the use of the SDK.
Q: What debuggers can I use for Windows development?
A: First of all, if you use Actor, Smalltalk or ToolBook, you're limited
to the debugging tools built into those packages. If you are using
C, C++ or another conventional language with Windows SDK, you have
several choices.
1. In real mode, you are limited to SYMDEB, which is pretty basic. It
also requires the use of a second monitor (monochrome for most
machines, 8514/A for MCA machines) or a serial terminal. SYMDEB
is included with the Windows SDK.
2. In standard mode, you can also use Codeview for Windows (CVW), or
Logitech's announced-but-not-yet-shipping MultiScope. CVW, which
is similar to the DOS version of Codeview, requires a secondary
monitor; a serial terminal can not be used. CVW is included with
the Windows SDK; MultiScope is a separate product.
3. If you have a 386, you have an additional option of using WDEB386,
which provides some further debugging features over CVW, at the
expense of an antiquated user interface. WDEB386, which is included
with the SDK, will work wither with a secondary monitor or a serial
terminal.
4. What does Windows do with my extended memory? After I run Windows,
Norton SI reports that I don't have any extended memory. Is this
a bug?
>> No, it's not a bug. Windows uses a memory-management system known
as DPMI, which requires applications to access extended memory
using a mechanism known as "XMS". This mechanism is implemented in
himem.sys. If you have device=himem.sys in your config.sys, the
first XMS call (by Windows or SmartDrive, for example) will transfer
control of the extended memory to himem.sys, and thus make it in-
accessible to non-XMS applications.
5. How can I take a snapshot of my Windows screen?
>> Simple -- just pres PrtScr, and Windows will copy the image to the
clipboard, from where you can paste it into your favourite application.
--------------------
6. Topics in the comp.windows.ms companion posting
>> 1. Windows newsgroups
2. Free Windows applications
3. Getting Windows video drivers
4. Using a mail server instead of ftp
5. Windows memory requirements
6. Standard mode vs. 386 enhanced mode
7. Running Windows 2.x applications
8. DOS in a window
9. Environment space in DOS sessions
10. Lotus 1-2-3 under Windows
11. DesqView/386 with Windows
12. Protected-mode software vs. Windows
13. Windows, Korn shell and switchar
14. Windows network compatability
15. Using COM3 or COM4 from Windows
16. Accessing the mouse in DOS sessions
17. Using TSRs for DOS sessions
18. 256 colours in Windows
19. Windows communications programs
20. Changing an application's icon
21. Creating new icons
22. Icon and bitmap directories
23. Installing new fonts
24. FaceLift, ATM and TrueType
25. Converting a GIF or MS-Paint file to a bitmap
26. Using a bitmap as wallpaper