pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) (03/09/91)
Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together. I run 386MAX 5.1 and when I run bcx my machine reboots!! I have a HP VECTRA RS25 (25 MHZ 386) -- Pat Fulghum 208-323-2667
alanr@tekig5.PEN.TEK.COM (Alan N Rovner) (03/11/91)
In article <11880003@hpdmd48.boi.hp.com> pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) writes: > >Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together. > >I run 386MAX 5.1 and when I run bcx my machine reboots!! > I have tried this too, and while my machine doesn't do anything drastic like reboot, I do get an error message about an incompatible memory manager is installed. I guess BCX incorporates its own DOS extender or memory manager that's incompatible with 386^max. Al Rovner Tektronix Inc. Beaverton, Ore.
dmatlock@eecs.cs.pdx.edu (Delbert Matlock) (03/12/91)
alanr@tekig5.PEN.TEK.COM (Alan N Rovner) writes: >In article <11880003@hpdmd48.boi.hp.com> pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) writes: >I have tried this too, and while my machine doesn't do anything drastic like >reboot, I do get an error message about an incompatible memory manager >is installed. I guess BCX incorporates its own DOS extender or memory manager >that's incompatible with 386^max. 386 To the MAX run the computer in 386 enhanced mode (yes, just like Windows), so you'll get the same effect with BCX under 386 MAX as you would under Windows running in enhanced mode. Try running just straight BC under 386 MAX, it will LOVE the expanded memory the MAX generates. ============================================================================= Delbert Matlock Internet: dmatlock@eecs.cs.pdx.edu MicroNet Northwest Voice: (503)228-3071
jim@shograf.COM (jim morris) (03/13/91)
From article <1545@tekig7.MAP.TEK.COM>, by alanr@tekig5.PEN.TEK.COM (Alan N Rovner): > In article <11880003@hpdmd48.boi.hp.com> pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) writes: >> >>Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together. >> >>I run 386MAX 5.1 and when I run bcx my machine reboots!! >> > > I have tried this too, and while my machine doesn't do anything drastic like > reboot, I do get an error message about an incompatible memory manager > is installed. I guess BCX incorporates its own DOS extender or memory manager > that's incompatible with 386^max. Well this is STRANGE... I have 386MAX 5.1, and when I run BCX it runs fine, it even manages to use VCPI to get the Expanded memory 386MAX is managing, and convert it to extended, (At least the get info says I have 4Mb when I have only reserved 700k extended memory). my 386max.pro file is:- ROM=C000-C800 EXT=2247 ; save 2Mb for Hyperdisk, 700k for BCX This seems to work for me!! -- Jim Morris, E-Mail: jim@shograf.com Voice: (415) 903-3887 _ SHO graphics. Practical PEX
mlord@bwdls58.bnr.ca (Mark Lord) (03/15/91)
<>Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together. <> <>I run 386MAX 5.1 and when I run bcx my machine reboots!! < <I have tried this too, and while my machine doesn't do anything drastic like <reboot, I do get an error message about an incompatible memory manager <is installed. I guess BCX incorporates its own DOS extender or memory manager <that's incompatible with 386^max. While my bcc BC++ upgrade has yet to arrive, the printed info I received from Borland indicates that BCX uses the VCPI standard for DOS extenders. This is the one that was as close as anything to "industry standard" before MicroSnot came out with "DPMI". So the question is.. does 386MAX claim to be VCPI compliant? Apparently QEMM 5.x is fully VCPI compliant, so I would imagine that QEMM users ought to have no problems with BCX. Since I use QEMM 5.11, I guess I'll find out more as soon as BC++ arrives. -- MLORD@BNR.CA Ottawa, Ontario *** Personal views only *** begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS <^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5 `` end
m1phm02@fed.frb.gov (Patrick H. McAllister) (03/16/91)
In article <559@shograf.COM> jim@shograf.COM (jim morris) writes: From article <1545@tekig7.MAP.TEK.COM>, by alanr@tekig5.PEN.TEK.COM (Alan N Rovner): > In article <11880003@hpdmd48.boi.hp.com> pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) writes: >> >>Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together. >> >>I run 386MAX 5.1 and when I run bcx my machine reboots!! >> > > I have tried this too, and while my machine doesn't do anything drastic like > reboot, I do get an error message about an incompatible memory manager > is installed. I guess BCX incorporates its own DOS extender or memory manager > that's incompatible with 386^max. Well this is STRANGE... I have 386MAX 5.1, and when I run BCX it runs fine, it even manages to use VCPI to get the Expanded memory 386MAX is managing, and convert it to extended, (At least the get info says I have 4Mb when I have only reserved 700k extended memory). . . . Even without any fancy memory manager like 386^MAX, bcx seems to consistently crash my machine. The setup: Northgate 486/33 w/ 8 megs, standard Windows/ Himem/Smartdrv, no interesting TSRs. If I go into bcx and rearrange or add editor windows, I am almost guaranteed to quickly die with a global protection fault. Something (the DOS extender, I assume) issues some messages about not being able to remove TKERNEL.EXE (this is bcx's memory manager) and then either locks up the machine (sometimes beyond even the reach of the three-finger salute) or leaves it with no available application memory. Does this sound familiar to anyone? Pat
danderer@brahms.udel.edu (Dave Anderer) (03/16/91)
In article <M1PHM02.91Mar15112950@mfsss1.fed.frb.gov> m1phm02@fed.frb.gov (Patrick H. McAllister) writes: > >Even without any fancy memory manager like 386^MAX, bcx seems to consistently >crash my machine. The setup: Northgate 486/33 w/ 8 megs, standard Windows/ >Himem/Smartdrv, no interesting TSRs. If I go into bcx and rearrange or add >editor windows, I am almost guaranteed to quickly die with a global protection >fault. I'm real familiar with this, in a very different hardware environment: a 'real' IBM AT, 2.6 Mb RAM, Himem. I get the same behavior with and without windows. Borland Tech Support had no ideas. My experience is it MIGHT depend on how much extended memory I allocate to TKERNEL. It MIGHT be the case that giving TKERNEL more memory makes me hang less often. -- Dave Anderer danderer@brahms.udel.edu (302) 451-8805 Instructional Technology Center, University of Delaware, Newark, De. 19716 "Sinners can repent; stupid is forever."
m1phm02@fed.frb.gov (Patrick H. McAllister) (03/18/91)
In article <19706@brahms.udel.edu> danderer@brahms.udel.edu (Dave Anderer) writes:
[quotes me re: problems with bcx . . .]
I'm real familiar with this, in a very different hardware environment:
a 'real' IBM AT, 2.6 Mb RAM, Himem. I get the same behavior with
and without windows.
Borland Tech Support had no ideas. My experience is it MIGHT depend
on how much extended memory I allocate to TKERNEL. It MIGHT be
the case that giving TKERNEL more memory makes me hang less often.
After a lot of playing around with config.sys, I managed to isolate the
problem to the Microsoft mouse driver. I called Borland tech support, and
the person there said, "Yes, we know we have problems with the Microsoft
mouse; we suggest that you buy another one. We like Logitech." I plan to
give them back their program, instead. Anyone have any other C compilers
that they like for writing Windows programs?
Patpwt@otter.hpl.hp.com (Peter Toft) (03/19/91)
Even without any fancy memory manager like 386^MAX, bcx seems to consistently crash my machine. The setup: Northgate 486/33 w/ 8 megs, standard Windows/ Himem/Smartdrv, no interesting TSRs. If I go into bcx and rearrange or add editor windows, I am almost guaranteed to quickly die with a global protection fault. Something (the DOS extender, I assume) issues some messages about not being able to remove TKERNEL.EXE (this is bcx's memory manager) and then either locks up the machine (sometimes beyond even the reach of the three-finger salute) or leaves it with no available application memory. Does this sound familiar to anyone? Pat Did you load the Borland tkernel.exe before starting windows in standard mode? You need a line like 'tkernel hi=yes kilos=1000'. If you do this, your memory setup will be much the same as mine, and I've had no problems. Peter =============================================================================== Peter Toft, ARPANET pwt@hplb.hpl.hp.com Hewlett-Packard Laboratories, JANET pwt@lb.hp.co.uk Filton Road, UUCP ...!mcvax!ukc!hplb!pwt Stoke Gifford, CSNET pwt%hplb.csnet@relay.cs.net Bristol. HPdesk Peter TOFT / HPC600 / 05 BS12 6QZ. Phone UK (0272) 799910 ext 24245 United Kingdom. Int'l +44 272 799910 ext 24245