ORCAD background color change
John Fields
I'm using, and dearly love, old ORCAD SDT in an XP DOS window, and it
works great.
But...
While ORCAD allows almost all of SDT's features' colors to be changed,
the black background cannot, as far as I can tell.
I'd like to change it to white.
Clue, please?
JF
Jim Thompson
I'm pretty sure that it can be done, but I last used SDT about 20
years ago. :-)
I have a copy on this machine, only to use the templates and symbol
libraries, to do conversions of old SDT stuff to PSpice Schematics.
Aren't all the colors in an CFG file?
It's coming back :-)
Use GENDRIVE.EXE to roll your own video driver.
...Jim Thompson
--
| James E.Thompson, CTO | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona 85048 Skype: Contacts Only | |
| Voice:(480)460-2350 Fax: Available upon request | Brass Rat |
| E-mail Icon at http://www.analog-innovations.com | 1962 |
I love to cook with wine. Sometimes I even put it in the food.
Joerg
Strictly from memory, way back: IIRC the only way one could change the
background color on SDT was to muck with the table stored in the
graphics card. But having anything other than black was frowned upon by
Orcadians back then, right up there with parking a Harley next to a
Goldwing ;-)
I don't know if this is still possible in a DOS window.
--
Regards, Joerg
http://www.analogconsultants.com/
"gmail" domain blocked because of excessive spam.
Use another domain or send PM.
MooseFET
I just looked in the ESP version and there is no background color
setting.
I don't have a working copy of the pre ESP version to check.
AwlSome Auger
<jfi...@austininstruments.com> wrote:
There was nothing when executed with "Orcad.exe -c"? That should bring
up the config menu selections, but I do not know if that is where it is
at either.
I'll fire it up and check a bit.
AwlSome Auger
<To-Email-Use-Th...@My-Web-Site.com> wrote:
>It's coming back :-)
>
>Use GENDRIVE.EXE to roll your own video driver.
>
> ...Jim Thompson
That has nothing to do with it.
AwlSome Auger
Err... that was "Draft.exe" and "/c" not "-c".
Anyway, the color table does not allow the Bkgd to be changed. It is
hard coded. I suppose it is possible to modify a driver if one knew how
they were compiled, which we do not. What is wrong with black?
My favorite console color scheme in Linux is Green on Black. :-)
Boris Mohar
>John Fields wrote:
>> OK, dammit, I'm stuck...
>>
>> I'm using, and dearly love, old ORCAD SDT in an XP DOS window, and it
>> works great.
>>
>> But...
>>
>> While ORCAD allows almost all of SDT's features' colors to be changed,
>> the black background cannot, as far as I can tell.
>>
>> I'd like to change it to white.
>>
>> Clue, please?
>>
>
>Strictly from memory, way back: IIRC the only way one could change the
>background color on SDT was to muck with the table stored in the
>graphics card. But having anything other than black was frowned upon by
>Orcadians back then, right up there with parking a Harley next to a
>Goldwing ;-)
>
>I don't know if this is still possible in a DOS window.
Ask in http://groups.yahoo.com/group/OldDosOrcad/ They did a lot of work
on new drivers.
--
Boris
Pieyed Piper
Hell, all we need is a decent set of VESA drivers. I have trouble even
getting any of my 800x600 drivers working on any of these newer cards, so
even VGA must be "in a different place" in the card's set-up. VESA modes
always seem to work these days. So they need a vesa driver set.
Tango PCB has one. Pretty nice too. I run both that and Orcad from
within DOSBox, which does allow full screen sessions, even in Windows 7.
Any hardware hooks that are needed (even local machine stuff) can be
attached to via NET USE type commands if direct methods pose problems.
Joerg
In SDT it could not be changed.
Joerg
In the olden days we loaded our own color tables so you could change
almost any color that a program would generate. But you had to know the
inner workings of your video card. And there were some that required
caution, if you wrote to the wrong registers you could kill the card ...
*phut*
Jim Thompson
wrote:
>AwlSome Auger wrote:
>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>
>>
>>> It's coming back :-)
>>>
>>> Use GENDRIVE.EXE to roll your own video driver.
>>>
>>> ...Jim Thompson
>> That has nothing to do with it.
>
>
>In the olden days we loaded our own color tables so you could change
>almost any color that a program would generate. But you had to know the
>inner workings of your video card. And there were some that required
>caution, if you wrote to the wrong registers you could kill the card ...
>*phut*
Let me guess, "AwlSome Auger" is another nym of dipshit AlwaysWrong?
As I remember Gendrive, you ran it pulling in data from the provided
driver for your card, VGA in my case, then you could twiddle the color
tables and export as your own custom driver... JET.DRV in my case.
(I can't run it now, but I'll send this archive to JF and see if he
can use it.)
PKZIP (tm) FAST! Create/Update Utility Version 1.02 10-01-89
Copyright 1989 PKWARE Inc. All Rights Reserved. PKZIP/h for help
Searching ZIP: DRIVER.ZIP
Length Method Size Ratio Date Time CRC-32 Attr Name
------ ------ ----- ----- ---- ---- ------ ---- ----
5445 Implode 1919 65% 01-24-90 10:34 4dbfa993 --w DXF.DRV
1168 Implode 578 51% 01-24-90 10:15 5653867c --w EPSON.DRV
1251 Implode 644 49% 01-24-90 10:15 81660b10 --w
EPSONFX.DRV
1375 Implode 724 48% 01-24-90 10:16 806a9463 --w
EPSONFX2.DRV
1251 Implode 643 49% 01-24-90 10:16 ef99113d --w
EPSONMX.DRV
5829 Implode 1468 75% 10-25-89 03:22 dc359893 --w
GENDRIVE.DAT
15136 Implode 9212 40% 10-25-89 03:22 dc43211d --w
GENDRIVE.DRV
21482 Implode 11302 48% 10-25-89 03:22 b04d3bff --w
GENDRIVE.EXE
3968 Implode 1703 58% 01-24-90 10:39 489bddbb --w HI.DRV
4391 Implode 1915 57% 01-24-90 10:39 e911f9fa --w HP.DRV
4391 Implode 1917 57% 01-24-90 10:40 314a2112 --w HP2.DRV
1031 Implode 431 59% 01-24-90 10:18 3aca1bde --w
HPLASER1.DRV
1058 Implode 431 60% 01-24-90 10:18 5bd65158 --w
HPLASER2.DRV
1108 Implode 433 61% 01-24-90 10:19 e432beec --w
HPLASER3.DRV
1258 Implode 432 66% 01-24-90 10:19 3b021261 --w
HPLASER4.DRV
1035 Implode 438 58% 01-24-90 10:19 b7d50616 --w
HPLASER5.DRV
1062 Implode 439 59% 01-24-90 10:20 0e8879cd --w
HPLASER6.DRV
1112 Implode 440 61% 01-24-90 10:20 df1fe5cf --w
HPLASER7.DRV
1262 Implode 439 66% 01-24-90 10:20 5f1d9c42 --w
HPLASER8.DRV
1358 Implode 689 50% 01-24-90 10:26 d8d25d37 --w
LQ1000_2.DRV
5757 Implode 3504 40% 01-24-90 10:13 8d6cfbd0 --w
PLOTTER.DRV
9715 Implode 5719 42% 03-16-90 10:40 d1d55307 --w
PRINTER.DRV
1849 Implode 346 82% 01-24-90 10:28 b72aa9c4 --w RASTER.DRV
18589 Implode 9590 49% 03-06-90 03:23 3933119a --w TIGA.DRV
1435 Implode 740 49% 01-24-90 10:30 dcb88ae6 --w
TOSHIBA2.DRV
18161 Implode 7510 59% 10-05-89 09:29 5aa8f4d6 --w
VECT1280.DRV
18161 Implode 7511 59% 10-05-89 09:29 b1b27403 --w
VECT768.DRV
18161 Implode 7505 59% 10-05-89 09:29 21cc426b --w
VECTRXAT.DRV
18177 Implode 7526 59% 10-05-89 09:30 f9be855d --w
VECTRXPC.DRV
14625 Implode 8791 40% 05-05-89 16:08 442f8bd8 --w VGA640.DRV
14913 Implode 9213 39% 05-05-89 16:03 624b3465 --w
CPTFULL.DRV
14273 Implode 8450 41% 05-05-89 16:02 f10047a6 --w CPTHGC.DRV
3858 Implode 1610 59% 01-24-90 10:35 feaaed72 --w DXY101.DRV
3899 Implode 1644 58% 01-24-90 10:35 8f351bd6 --w DXY800.DRV
1279 Implode 635 51% 01-24-90 10:16 a1163f84 --w
EPSONVP.DRV
3853 Implode 1463 63% 01-24-90 10:37 5f8f7ea5 --w
GENERIC.DRV
2844 Implode 1096 62% 06-18-90 08:29 b618c3fd --w GERBER.DRV
2825 Implode 1083 62% 06-18-90 08:29 660205ec --w
GERBER2X.DRV
2870 Implode 1101 62% 06-18-90 08:29 bd7e126f --w
GERBER34.DRV
14369 Implode 8537 41% 05-05-89 16:04 f5bcf870 --w HGC2.DRV
3961 Implode 1700 58% 01-24-90 10:39 1cbaadbc --w HI29.DRV
1057 Implode 434 59% 01-24-90 10:17 5b28fbb8 --w HP2K1.DRV
1092 Implode 434 61% 01-24-90 10:17 ee63eb9b --w HP2K2.DRV
1157 Implode 435 63% 01-24-90 10:17 c05d5177 --w HP2K3.DRV
1354 Implode 436 68% 01-24-90 10:17 ebea09d2 --w HP2K4.DRV
1040 Implode 486 54% 02-26-87 23:26 13d66701 --w
HPLASER.DRV
4364 Implode 1888 57% 01-24-90 10:40 ce002383 --w HPX.DRV
1253 Implode 644 49% 01-24-90 10:25 ce096b5b --w
IBMCOLOR.DRV
4320 Implode 1815 58% 01-24-90 10:41 cfc17d9e --w
PSCRIPT.DRV
1562 Implode 812 49% 03-18-87 09:07 962393c4 --w RASTER.DOC
16113 Implode 9241 43% 05-05-89 16:08 97305b16 --w VEGA1K.DRV
14065 Implode 8135 43% 04-13-88 08:22 6f6031b8 --w
EGA16C1.DRV
14161 Implode 8215 42% 05-05-89 16:03 4f859fd4 --w
EGA16C2.DRV
14369 Implode 8498 41% 05-05-89 16:03 a8cf7660 --w EGA16E.DRV
14337 Implode 8466 41% 05-05-89 16:03 0351a212 --w EGA2.DRV
14369 Implode 8514 41% 05-05-89 16:04 91d7fb94 --w EGA4E.DRV
6192 Implode 4366 30% 03-06-90 03:23 b34fe7d4 --w
ADSLOAD.EXE
19328 Implode 10793 45% 03-06-90 03:23 5362ddf8 --w
ADSORCAD.COM
12481 Implode 7753 38% 03-06-90 03:23 4f3eddb1 --w
ADSVECTR.DRV
16097 Implode 9231 43% 05-01-90 03:23 a7d4b761 --w
AHEAD1K.DRV
15873 Implode 9044 44% 05-05-89 16:02 583d6c01 --w ATT16C.DRV
14305 Implode 8508 41% 05-05-89 16:02 6129caf8 --w ATT2C.DRV
16193 Implode 9391 43% 03-06-90 03:23 4f8676bb --w
CHIPS1K.DRV
1028 Implode 415 60% 01-24-90 10:18 46cab86f --w
HPINKJET.DRV
20577 Implode 8406 60% 03-06-90 03:23 f1c539ad --w DGIS.DRV
15136 Implode 9210 40% 04-20-90 12:26 c39e3432 --w
DISPLAYX.DRV
16081 Implode 9227 43% 05-01-90 03:23 0d09c218 --w
GEN641K.DRV
13777 Implode 7738 44% 05-05-89 16:04 dbb23c2b --w GENIUS.DRV
16097 Implode 9231 43% 05-05-89 16:04 9da2af37 --w
GENOA1K.DRV
13889 Implode 8062 42% 05-05-89 16:02 d791289f --w CGA2.DRV
15265 Implode 8485 45% 05-05-89 16:02 59a92b3e --w CGA4.DRV
4261 Implode 1793 58% 06-19-90 14:41 ba9883e9 --w PWORD.DRV
14337 Implode 8534 41% 05-05-89 16:04 d394ddf6 --w
HPVECTRA.DRV
14321 Implode 8607 40% 05-05-89 16:04 96aac0a9 --w
MCGA480.DRV
14721 Implode 8131 45% 05-05-89 16:05 b6fecf30 --w NCR2.DRV
16129 Implode 8618 47% 05-05-89 16:05 b6a9b985 --w NCR4.DRV
15665 Implode 9050 43% 05-05-89 16:10 c2631e4a --w
NEC9801C.DRV
14449 Implode 8620 41% 05-05-89 16:09 ffb73f27 --w
NEC9801M.DRV
15889 Implode 9022 44% 05-05-89 16:05 4e39ac1e --w
SIGMA400.DRV
14305 Implode 8496 41% 05-05-89 16:05 cc19eb60 --w T3100.DRV
14193 Implode 8432 41% 05-05-89 16:06 125d7a39 --w
TANDY2K.DRV
16081 Implode 9200 43% 05-08-89 13:03 56a5a33a --w
TECMAR1K.DRV
14417 Implode 8612 41% 05-05-89 16:06 eef4e77f --w
TELECAT.DRV
18241 Implode 9076 51% 05-05-89 16:06 3eec373d --w TGM16I.DRV
17809 Implode 8756 51% 05-05-89 16:06 2623eb2a --w TGM16N.DRV
15601 Implode 8880 44% 05-05-89 16:07 a38c168a --w TGM2I.DRV
14881 Implode 8386 44% 05-05-89 16:07 8d1f9db2 --w TGM2N.DRV
16353 Implode 8922 46% 05-05-89 16:07 c846cb2f --w TGM4I.DRV
15921 Implode 8616 46% 05-05-89 16:07 51bca2bd --w TGM4N.DRV
16097 Implode 9227 43% 03-06-90 03:23 924f349b --w TRI1K.DRV
1221 Implode 609 51% 01-24-90 10:13 4a89f702 --w AMT.DRV
1214 Implode 611 50% 01-24-90 10:13 095b5cd3 --w
AMT_ACEL.DRV
4085 Implode 1766 57% 01-24-90 10:33 7a3b44e6 --w
APPLE410.DRV
4863 Implode 1886 62% 01-24-90 10:33 ef0709af --w
CALCOMP1.DRV
4752 Implode 1821 62% 01-24-90 10:34 58cb6519 --w
CALCOMP2.DRV
1055 Implode 412 61% 01-24-90 10:14 78f02952 --w
CANON150.DRV
1215 Implode 416 66% 01-24-90 10:14 3f303e5e --w
CANON300.DRV
977 Implode 409 59% 01-24-90 10:13 6f452c2b --w
CANON75.DRV
1301 Implode 677 48% 01-24-90 10:14 49161c4b --w
CITH1550.DRV
1295 Implode 676 48% 01-24-90 10:15 42efdbba --w
CITOH310.DRV
4569 Implode 1960 58% 06-19-90 14:39 bc204b88 --w EPS1.DRV
4596 Implode 1983 57% 06-19-90 14:40 891d5f10 --w EPS2.DRV
4569 Implode 1961 58% 06-19-90 14:40 2d14fd2f --w EPS3.DRV
4555 Implode 1952 58% 06-19-90 14:41 e7534654 --w EPS4.DRV
1041 Implode 438 58% 01-24-90 10:20 a0a31d03 --w
HPDESK1.DRV
1068 Implode 438 59% 01-24-90 10:21 a4af59e3 --w
HPDESK2.DRV
1119 Implode 441 61% 01-24-90 10:21 8a127852 --w
HPDESK3.DRV
1269 Implode 439 66% 01-24-90 10:21 354d96ec --w
HPDESK4.DRV
1040 Implode 439 58% 01-24-90 10:22 4ffda1c4 --w
HPDESK5.DRV
1067 Implode 440 59% 01-24-90 10:22 e2f8a0a3 --w
HPDESK6.DRV
1118 Implode 443 61% 01-24-90 10:22 dc781f00 --w
HPDESK7.DRV
1268 Implode 441 66% 01-24-90 10:23 4e8eb9cb --w
HPDESK8.DRV
1140 Implode 437 62% 01-24-90 10:24 ba87d8fe --w
HPPAINT1.DRV
1139 Implode 440 62% 01-24-90 10:24 422df89d --w
HPPAINT2.DRV
1106 Implode 432 61% 01-24-90 10:23 e9eaab3d --w
HPQUIET1.DRV
1264 Implode 431 66% 01-24-90 10:23 087b2bb7 --w
HPQUIET2.DRV
1110 Implode 430 62% 01-24-90 10:24 19d81125 --w
HPQUIET3.DRV
1268 Implode 431 67% 01-24-90 10:24 2dc96b6f --w
HPQUIET4.DRV
1217 Implode 590 52% 01-24-90 10:25 244abcbf --w JDL750.DRV
1221 Implode 595 52% 01-24-90 10:25 c9612a15 --w JDL850.DRV
1235 Implode 608 51% 01-24-90 10:26 0bb263ef --w LQ1000.DRV
1295 Implode 665 49% 01-24-90 10:26 3313b52c --w
NEC8023.DRV
1276 Implode 630 51% 01-24-90 10:27 304ab2dc --w
NECPR201.DRV
1446 Implode 776 47% 01-24-90 10:27 b3114c90 --w OKI192.DRV
1408 Implode 741 48% 01-24-90 10:28 13516f7d --w
OKI2410.DRV
1408 Implode 739 48% 01-24-90 10:27 58b999b0 --w OKI92.DRV
19466 Implode 9994 49% 04-17-90 03:23 24fe3cd9 --w
PLT2IGES.EXE
4322 Implode 1815 59% 01-24-90 10:41 c6859665 --w
PSCRIPT2.DRV
1262 Implode 654 49% 01-24-90 10:28 58d96149 --w STAR10.DRV
1258 Implode 647 49% 01-24-90 10:29 973ba258 --w
TALLY80.DRV
1255 Implode 645 49% 01-24-90 10:29 b30a1de5 --w TI850.DRV
1272 Implode 630 51% 05-01-90 16:39 d90bdc42 --w
TOSHIBA.DRV
1446 Implode 402 73% 01-24-90 10:30 bb7e4756 --w
VERSATEC.DRV
4006 Implode 1721 58% 01-24-90 10:42 70c445d7 --w WG.DRV
14225 Implode 8471 41% 05-05-89 16:09 47e582ac --w
WYSE700A.DRV
14225 Implode 8477 41% 05-05-89 16:09 c5029ff8 --w
WYSE700B.DRV
15473 Implode 9028 42% 05-05-89 16:09 5de60a5a --w
WYSE700C.DRV
------ ------ --- -------
1015148 539849 47% 137
Spehro Pefhany
<inv...@invalid.invalid> wrote:
>AwlSome Auger wrote:
>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>
>>
>>> It's coming back :-)
>>>
>>> Use GENDRIVE.EXE to roll your own video driver.
>>>
>>> ...Jim Thompson
>> That has nothing to do with it.
>
>
>In the olden days we loaded our own color tables so you could change
>almost any color that a program would generate. But you had to know the
>inner workings of your video card. And there were some that required
>caution, if you wrote to the wrong registers you could kill the card ...
>*phut*
Don't remember that.. but do remember that some CRT monitors would die
if fed the wrong horiz/vert frequencies (which some cards were quite
capable of producing).
Best regards,
Spehro Pefhany
--
"it's the network..." "The Journey is the reward"
sp...@interlog.com Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog Info for designers: http://www.speff.com
Jim Thompson
<spef...@interlogDOTyou.knowwhat> wrote:
>On Sat, 13 Feb 2010 13:38:01 -0800, the renowned Joerg
><inv...@invalid.invalid> wrote:
>
>>AwlSome Auger wrote:
>>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>>
>>>
>>>> It's coming back :-)
>>>>
>>>> Use GENDRIVE.EXE to roll your own video driver.
>>>>
>>>> ...Jim Thompson
>>> That has nothing to do with it.
>>
>>
>>In the olden days we loaded our own color tables so you could change
>>almost any color that a program would generate. But you had to know the
>>inner workings of your video card. And there were some that required
>>caution, if you wrote to the wrong registers you could kill the card ...
>>*phut*
>
>Don't remember that.. but do remember that some CRT monitors would die
>if fed the wrong horiz/vert frequencies (which some cards were quite
>capable of producing).
>
>
>
>Best regards,
>Spehro Pefhany
See my post as regards using Gendrive to create your own color tables
_on_the_driver_for_your_card_.
AwlSome Auger
wrote:
>MooseFET wrote:
>> On Feb 12, 1:21 pm, John Fields <jfie...@austininstruments.com> wrote:
>>> OK, dammit, I'm stuck...
>>>
>>> I'm using, and dearly love, old ORCAD SDT in an XP DOS window, and it
>>> works great.
>>>
>>> But...
>>>
>>> While ORCAD allows almost all of SDT's features' colors to be changed,
>>> the black background cannot, as far as I can tell.
>>>
>>> I'd like to change it to white.
>>>
>>> Clue, please?
>>>
>>
>> I just looked in the ESP version and there is no background color
>> setting.
>> I don't have a working copy of the pre ESP version to check.
>
>
>In SDT it could not be changed.
Unable to change it through menus. There may be a way to hack the
driver, but I doubt it.
My Tango PCB works perfectly with DOSBox, and the VESA1280 driver.
I attribute this to my video card maker, EVGA.
AwlSome Auger
wrote:
>AwlSome Auger wrote:
>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>
>>
>>> It's coming back :-)
>>>
>>> Use GENDRIVE.EXE to roll your own video driver.
>>>
>>> ...Jim Thompson
>> That has nothing to do with it.
>
>
>In the olden days we loaded our own color tables so you could change
>almost any color that a program would generate. But you had to know the
>inner workings of your video card. And there were some that required
>caution, if you wrote to the wrong registers you could kill the card ...
>*phut*
In the days of memory arrays that stored frames within 1024kB of space,
sure.
Nowadays, full VESA compliance might be nebulous with some of the gamer
card makers. Forget TIGA compliance.
Anyway, Gendrive.exe did not have any range of function to speak of,
and certainly did not allow tweaking of registers, and color table
translations.
I will post the driver I have had the most success with in trying to
get it at 800x600, which is about all we could ever hope for. It is SDT
3.21
AwlSome Auger
<To-Email-Use-Th...@My-Web-Site.com> wrote:
>As I remember Gendrive, you ran it pulling in data from the provided
>driver for your card,
That's going to do a lot of good for cards without "provided drivers"
to "pull in from".
Bwuahahahahaha.
You cannot even get logic right when you are guessing at it.
The applet is for generating a driver when there is NO provided driver
in place. DOH!
Jim Thompson
<spef...@interlogDOTyou.knowwhat> wrote:
>On Sat, 13 Feb 2010 13:38:01 -0800, the renowned Joerg
><inv...@invalid.invalid> wrote:
>
>>AwlSome Auger wrote:
>>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>>
>>>
>>>> It's coming back :-)
>>>>
>>>> Use GENDRIVE.EXE to roll your own video driver.
>>>>
>>>> ...Jim Thompson
>>> That has nothing to do with it.
>>
>>
>>In the olden days we loaded our own color tables so you could change
>>almost any color that a program would generate. But you had to know the
>>inner workings of your video card. And there were some that required
>>caution, if you wrote to the wrong registers you could kill the card ...
>>*phut*
>
>Don't remember that.. but do remember that some CRT monitors would die
>if fed the wrong horiz/vert frequencies (which some cards were quite
>capable of producing).
>
>
>
>Best regards,
>Spehro Pefhany
Joerg has a *phutish* ;-)
Here's the skinny just as I remembered...
http://analog-innovations.com/SED/OrCAD_Gendrive_Info.pdf
Joerg
Yes, that's how it's done. I never killed a graphics card with it but in
the old days it was possible with some of them to drive them into a bus
contention situation. Then it would sit there and some chip would become
toasty, hot, hotter, really hot ...
Joerg
> On Sat, 13 Feb 2010 13:38:01 -0800, Joerg <inv...@invalid.invalid>
> wrote:
>
>> AwlSome Auger wrote:
>>> On Fri, 12 Feb 2010 14:36:28 -0700, Jim Thompson
>>> <To-Email-Use-Th...@My-Web-Site.com> wrote:
>>>
>>>
>>>> It's coming back :-)
>>>>
>>>> Use GENDRIVE.EXE to roll your own video driver.
>>>>
>>>> ...Jim Thompson
>>> That has nothing to do with it.
>>
>> In the olden days we loaded our own color tables so you could change
>> almost any color that a program would generate. But you had to know the
>> inner workings of your video card. And there were some that required
>> caution, if you wrote to the wrong registers you could kill the card ...
>> *phut*
>
>
> In the days of memory arrays that stored frames within 1024kB of space,
> sure.
>
> Nowadays, full VESA compliance might be nebulous with some of the gamer
> card makers. Forget TIGA compliance.
>
> Anyway, Gendrive.exe did not have any range of function to speak of,
> and certainly did not allow tweaking of registers, and color table
> translations.
>
But the manual says so ... :-)
[...]
Jim Thompson
wrote:
I just knew I had done it, because I absolutely despise black
backgrounds... almost as much as I hate white text on a blue
background ;-)
>I never killed a graphics card with it but in
>the old days it was possible with some of them to drive them into a bus
>contention situation. Then it would sit there and some chip would become
>toasty, hot, hotter, really hot ...
I never attempted to tweak anything other than the color palette.
Joerg
I actually liked the black background.
>> I never killed a graphics card with it but in
>> the old days it was possible with some of them to drive them into a bus
>> contention situation. Then it would sit there and some chip would become
>> toasty, hot, hotter, really hot ...
>
> I never attempted to tweak anything other than the color palette.
>
As Spehro mentioned, the real danger was tweaking the frame rate and
number of lines. Losing a $200 graphics card is one thing but having the
flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ... *PHOOF*
was quite another.
Jim Thompson
wrote:
My last few CRT monitors were multi-sync... unfortunately so heavy it
took two people to move them ;-)
Joel Koltner
news:7tosu8...@mid.individual.net...
> As Spehro mentioned, the real danger was tweaking the frame rate and number
> of lines. Losing a $200 graphics card is one thing but having the flyback
> xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ... *PHOOF* was quite
> another.
Possibly silly question: In a $2k monitor, would it have really cost very much
(relatively speaking) to prevent the flyback transformer from frying?
Is it the core going into saturation that kills them (overheating leading to
insulation being lost and eventually shorting) or too high output voltage
(leading directly to shorting)?
Peter McMullin
WHAT BORIS SAID. You're not paying attention. What driver would you like?
>> Ask in http://groups.yahoo.com/group/OldDosOrcad/ They did a lot of
>> work
>>on new drivers.
And, they're all available in the files area. Life is good.
OrCad lives on, and produces.You don't need dosbox under XP. Don't know
about W7. Sorry if this does not address the OP's question directly, but
actually it does.
-Peter
Pieyed Piper
wrote:
>And, they're all available in the files area. Life is good.
>OrCad lives on, and produces.You don't need dosbox under XP. Don't know
>about W7. Sorry if this does not address the OP's question directly, but
>actually it does.
DOSBox allows one to use vesa drivers, and it also can translate
between a driver and your actual card, which almost always differs these
days.
A straight XP DOS window, which not everyone has, does not necessarily
allow such behavior. Very few of the cards in the list are still in use
at all. Even though I own a few, that is beside the point. XP doesn't
run on the machines that those cards do run on.
Joerg
> "Joerg" <inv...@invalid.invalid> wrote in message
> news:7tosu8...@mid.individual.net...
>> As Spehro mentioned, the real danger was tweaking the frame rate and
>> number of lines. Losing a $200 graphics card is one thing but having
>> the flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ...
>> *PHOOF* was quite another.
>
> Possibly silly question: In a $2k monitor, would it have really cost
> very much (relatively speaking) to prevent the flyback transformer from
> frying?
>
No, but it would probably have caused the BOM budget limit to be
exceeded by 15 Cents :-)
> Is it the core going into saturation that kills them (overheating
> leading to insulation being lost and eventually shorting) or too high
> output voltage (leading directly to shorting)?
>
I don't know, maybe some sort of resonance. What people described was
that it "hissed", kept working for a while, and then p...p..popp ... poof.
Spehro Pefhany
<inv...@invalid.invalid> wrote:
>Joel Koltner wrote:
>> "Joerg" <inv...@invalid.invalid> wrote in message
>> news:7tosu8...@mid.individual.net...
>>> As Spehro mentioned, the real danger was tweaking the frame rate and
>>> number of lines. Losing a $200 graphics card is one thing but having
>>> the flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ...
>>> *PHOOF* was quite another.
>>
>> Possibly silly question: In a $2k monitor, would it have really cost
>> very much (relatively speaking) to prevent the flyback transformer from
>> frying?
>>
>
>No, but it would probably have caused the BOM budget limit to be
>exceeded by 15 Cents :-)
>
>
>> Is it the core going into saturation that kills them (overheating
>> leading to insulation being lost and eventually shorting) or too high
>> output voltage (leading directly to shorting)?
>>
>
>I don't know, maybe some sort of resonance. What people described was
>that it "hissed", kept working for a while, and then p...p..popp ... poof.
Then a resounding Ka-Ching! (or so I hear).
Jim Thompson
<spef...@interlogDOTyou.knowwhat> wrote:
>On Sun, 14 Feb 2010 09:46:58 -0800, the renowned Joerg
><inv...@invalid.invalid> wrote:
>
>>Joel Koltner wrote:
>>> "Joerg" <inv...@invalid.invalid> wrote in message
>>> news:7tosu8...@mid.individual.net...
>>>> As Spehro mentioned, the real danger was tweaking the frame rate and
>>>> number of lines. Losing a $200 graphics card is one thing but having
>>>> the flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ...
>>>> *PHOOF* was quite another.
>>>
>>> Possibly silly question: In a $2k monitor, would it have really cost
>>> very much (relatively speaking) to prevent the flyback transformer from
>>> frying?
>>>
>>
>>No, but it would probably have caused the BOM budget limit to be
>>exceeded by 15 Cents :-)
>>
>>
>>> Is it the core going into saturation that kills them (overheating
>>> leading to insulation being lost and eventually shorting) or too high
>>> output voltage (leading directly to shorting)?
>>>
>>
>>I don't know, maybe some sort of resonance. What people described was
>>that it "hissed", kept working for a while, and then p...p..popp ... poof.
>
>Then a resounding Ka-Ching! (or so I hear).
>
>
>Best regards,
>Spehro Pefhany
Joerg should hire himself out as a sound effects man for the movie
industry... put all that hissing, popping, poofing and "phuting" to go
use ;-)
Joerg
> On Sun, 14 Feb 2010 09:46:58 -0800, the renowned Joerg
> <inv...@invalid.invalid> wrote:
>
>> Joel Koltner wrote:
>>> "Joerg" <inv...@invalid.invalid> wrote in message
>>> news:7tosu8...@mid.individual.net...
>>>> As Spehro mentioned, the real danger was tweaking the frame rate and
>>>> number of lines. Losing a $200 graphics card is one thing but having
>>>> the flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ...
>>>> *PHOOF* was quite another.
>>> Possibly silly question: In a $2k monitor, would it have really cost
>>> very much (relatively speaking) to prevent the flyback transformer from
>>> frying?
>>>
>> No, but it would probably have caused the BOM budget limit to be
>> exceeded by 15 Cents :-)
>>
>>
>>> Is it the core going into saturation that kills them (overheating
>>> leading to insulation being lost and eventually shorting) or too high
>>> output voltage (leading directly to shorting)?
>>>
>> I don't know, maybe some sort of resonance. What people described was
>> that it "hissed", kept working for a while, and then p...p..popp ... poof.
>
> Then a resounding Ka-Ching! (or so I hear).
>
Aggravated by the fact that you could not easily buy a spare HV flyback
transformer for a computer monitor. With TV sets they could be had for
$30-$60, usually. Ok, sometimes you had to pretend you were a TV repair
pro and don a white coat, or send a friend to buy it.
Jim Thompson
wrote:
[snip]
>
>Aggravated by the fact that you could not easily buy a spare HV flyback
>transformer for a computer monitor. With TV sets they could be had for
>$30-$60, usually. Ok, sometimes you had to pretend you were a TV repair
>pro and don a white coat, or send a friend to buy it.
Back when I bothered to repair my own stuff I'd just call my father.
He would recite the chassis number and the failure mechanism, and send
me the part, along with exact instructions ;-)
Joerg
> On Sun, 14 Feb 2010 13:40:06 -0800, Joerg <inv...@invalid.invalid>
> wrote:
>
> [snip]
>> Aggravated by the fact that you could not easily buy a spare HV flyback
>> transformer for a computer monitor. With TV sets they could be had for
>> $30-$60, usually. Ok, sometimes you had to pretend you were a TV repair
>> pro and don a white coat, or send a friend to buy it.
>
> Back when I bothered to repair my own stuff I'd just call my father.
> He would recite the chassis number and the failure mechanism, and send
> me the part, along with exact instructions ;-)
>
I can picture that. "Now, son, listen up! This ain't no chip design
where you type something into a computation machine and lean back, this
is real work ..."
My dad regularly gave me lectures when I, for example, showed up to our
oh-so-much-fun oil furnace repair sessions. Armed with nothing but a
pipe wrench and a hammer. "You electrical guys aren't supposed to handle
every screw with a pipe wrench ..."
krw
<To-Email-Use-Th...@My-Web-Site.com> wrote:
>On Sun, 14 Feb 2010 13:40:06 -0800, Joerg <inv...@invalid.invalid>
>wrote:
>
>[snip]
>>
>>Aggravated by the fact that you could not easily buy a spare HV flyback
>>transformer for a computer monitor. With TV sets they could be had for
>>$30-$60, usually. Ok, sometimes you had to pretend you were a TV repair
>>pro and don a white coat, or send a friend to buy it.
>
>Back when I bothered to repair my own stuff I'd just call my father.
>He would recite the chassis number and the failure mechanism, and send
>me the part, along with exact instructions ;-)
THe guy I worked for in college was like that. He'd get telephone
calls all day. The caller would give him the make, model, and symptom
and he'd recite the chassis numbers, parts to change (including part
numbers for the common stuff) back to the person calling. Amazing.
Michael A. Terrell
Joerg wrote:
>
> As Spehro mentioned, the real danger was tweaking the frame rate and
> number of lines. Losing a $200 graphics card is one thing but having the
> flyback xfmr of a $2k monitor go phseeeeoooouuu ... phsssst ... *PHOOF*
> was quite another.
The original monochrome monitor used on the early IBM PCs would die
if it lost horizontal drive. That is why PC/XT power supplies had a
switched power outlet for monitor. I had a couple damaged by customers
that way. Needless to say, the replacement monitors were more ID10T
proof.
--
Greed is the root of all eBay.
JosephKK
I expect that the "support" for the short list of cards amounts to providing
emulations of them. Not a promise to use them.
Pieyed Piper
wrote:
The drivers and the list were made before the term 'emulation' was even
used in the CAD industry. It was a single session world.
JosephKK
Gibberish from the unwilling to read.
life imitates life
wrote:
You're an idiot. There is no support. It is a dead application. It
died way back when the hardware it runs on died, so the list is of that
hardware, dipshit. Promise us you'll try to have a brain in your next
life. Your peanut gallery horseshit is what is gibberish.