Liren Large Software Subsidy 15

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 15 / 15.iso / s / s205 / 1.ddi / BACKUP.001 / DOC_IREF_SOFTWARE.FIX < prev next >

Wrap

Text File | 1991-03-11 | 23.1 KB | 521 lines

--------------------------------------------------------------------------- Report = 1374 Program = BPP.EXE MKT1.0 INTERNAL TABLES INCORRECTLY DESCRIBE THE PAIRING PRESENT IN THE MACH210 DEVICE. SPECIFICALLY, THE NODE TO PIN MAPPING OF QUADRANTS B & D ARE REVERSED, MSB TO LSB. --------------------------------------------------------------------------- Report = 1386 Program = BPP.EXE MKT1.0 MEMORY CORRUPTION ERROR: DESIGN CAUSES PROGRAM TO GENERATE THE FF:MSG ZMALLOC:ERROR CODE 86, COUNT =00A0 (0062, 003E) BX = C499 CX = FCA0 DX = 0A5E SI = 00B8 DI = 4B7D PROGRAM TYPO MEMORY VIOLATION.(EPSON COMPUTER ONLY) --------------------------------------------------------------------------- Report = 1419 Program = BPP.EXE MKT1.0 INCORRECT PROCESSING OF RANGE OPERATOR: SIGNAL RAS[3.0] COMPILES/FITS INCORRECTLY WITH RAS[1] ONLY HAVING ONE PT USED. --------------------------------------------------------------------------- Report = 1539 Program = BPP.EXE MKT1.0 MEMORY CORRUPTION ERROR: DESIGN CAUSES PROGRAM TO GENERATE ZMALLOC:ERROR:CODE 89, COUNT = 0576 (0346, 0230) BX = 2029 CX = F9DO DX = 61BB SI = 29FD DI = 4B7D. --------------------------------------------------------------------------- Report = 1543 Program = BPP.EXE MKT1.0 PROGRAM GETS MEMORY CORRUPTION ERROR ON DESIGN FILE WHEN AN 'IF' STATEMENT HAS EMPTY 'BEGIN'-'END' BLOCK. --------------------------------------------------------------------------- Report = 1550 Program = BPP.EXE Rev1.B LARGE DESIGN CAUSED OUT OF MEMORY: FILES 3-01112A (SC_STATE), 3-01113A (SLAVE) RAN OUT OF MEMORY DURING THE PROGRAM EXECUTION. --------------------------------------------------------------------------- Report = 1645 Program = BPP.EXE MKT1.0 PROGRAM GETS MEMORY CORRUPTION ERROR ON DESIGN FILE WHEN AN 'CASE' STATEMENT HAS EMPTY 'BEGIN'-'END' BLOCK. --------------------------------------------------------------------------- Report = 695 Program = EXPAND.EXE MKT1.0 LARGE STATE MACHINE DESIGN CAUSES EXPAND TO STOP WITH AN "OUT OF MEMORY" MESSAGE. THIS DESIGN SHOULD EASILY FIT INTO MACH110 ONCE IT IS IN BOOLEAN FORM, (89 STATES = 7 STATE BITS & < 16 PT'S AT EACH STATE.) --------------------------------------------------------------------------- Report = 1320 Program = EXPAND.EXE MKT1.0 EXPAND GIVES OUT A WARNING: "E1310 MISSING DEFAULT NEXT STATE " FOR STATE WHEN YOU MISTYPE THE STATE NAME IN THE STATEMENT : DEFAULT_BRANCH <STATE_NAME> --------------------------------------------------------------------------- Report = 1460 Program = EXPAND.EXE MKT1.0 MEMORY CORRUPTION ERROR: GET ZMALLOC ERROR 89 ON A MACH110 FILE THAT HAS 2 STATE MACHINES. --------------------------------------------------------------------------- Report = 1551 Program = EXPAND.EXE Rev1.B LARGE STATE MACHINE DESIGN CAUSES EXPAND TO STOP WITH AN "OUT OF MEMORY" MESSAGE. --------------------------------------------------------------------------- Report = 1594 Program = EXPAND.EXE MKT1.0 A PLS105 DESIGN GETS: "SYSTEM ERROR Z5 INPUT MESSAGE FILE READ ERROR, MESSAGE NUMBER IS 2740". --------------------------------------------------------------------------- Report = 1211 Program = FITR.EXE MKT1.0 INPUT PAIRING ERROR FOR MACH210. IN EXAMPLE, FITR INDICATES: "PAIR EQUATION PROBLEM". --------------------------------------------------------------------------- Report = 1221 Program = FITR.EXE 4BETA ERROR F600 MESSAGE DESCRIPTION AND ERROR DATAPOINT RECOVERY REFER TO A LACK OF INPUT RESOURCES IN THE DESIGN. EXAMPLES HAVE INPUT RESOURCES BUT PERHAPS CONTAIN TOO MUCH FUNCTIONALITY. --------------------------------------------------------------------------- Report = 1269 Program = FITR.EXE MKT1.0 MACROCELL PLACEMENT DATA IS LOST BY THE FITR FOR PRE-PLACED NODE EQUATIONS IN DESIGN FILE. --------------------------------------------------------------------------- Report = 1270 Program = FITR.EXE MKT1.0 INTERNAL ERROR GENERATED FOR DESIGN FILE WHEN FITR IS MAKING A MACH210 JEDEC MAP. --------------------------------------------------------------------------- Report = 1351 Program = FITR.EXE MKT1.0 RUN - TIME ERROR 201 AT 0000:57C1 --------------------------------------------------------------------------- Report = 1418 Program = FITR.EXE MKT1.0 FITR PREMATURELY TERMINATED WITH A "RUNTIME ERROR 202", WHILE COMPILING/ FITTING MACH 210 DESIGN FILE, THIS DESIGN COMPILED AND FITTED SUCCESSFULLY ON BETA VERSION. --------------------------------------------------------------------------- Report = 1447 Program = FITR.EXE MKT 1.0 AFTER THE SUCCESSFUL FIT INTO A MACH210, THE REPORT FILE ALWAYS REPORTS ONE LESS PIN USED THAN ACTUAL. FOR EXAMPLE, IN REPORT FILE 35 OUT OF 38 PINS ARE SHOWN USED, WHEN ACTUALLY 36 WERE USED. NUMBER OF PINS IS CORRECT. --------------------------------------------------------------------------- Report = 1533 Program = FITR.EXE MKT1.0 GLOBAL ASSIGNMENT OF SET AND RESET WOULD SAVE SOME TYPING AND REDUCE CLUTTER IN THE FILE. --------------------------------------------------------------------------- Report = 1563 Program = FITR.EXE MKT1.0 NO JEDEC OUTPUT FILES ARE PROVIDED FOR MACH210 DEVICES. --------------------------------------------------------------------------- Report = 1583 Program = FITR.EXE Rev1.C FILE WILL FIT IF FITR USES OPTIONS "-E-F".WHEN RUNNING FITR FROM MENU, FITR WILL TRY ANOTHER FITR OPTION COMBINATION FIRST, CAUSING FITR TO ABORT.THIS THEN CAUSES MENU TO SKIP TRYING OTHER VALID FITR OPTION COMBINATIONS. --------------------------------------------------------------------------- Report = 1587 Program = FITR.EXE MKT1.0 WHEN PINS ARE ASSIGNED BY USER AND THE PLACEMENT SHOULD FIT. THE FITR TERMINATES WITH "FITTING UNSUCCESSFUL - 100%" AND MSG/CONDITION CAUSED JEDEC NOT TO BE GENERATED EVEN THOUGH DEVICE DID FIT. --------------------------------------------------------------------------- Report = 1598 Program = FITR.EXE Rev1.C FITR EXITS AFTER 2ND FITTING OPTION, EVEN THOUGH IT FITS ON THE 3RD OPTION. FITS WHEN OPTIONS; EXPAND SMALL-YES, MAX PACKING-YES, & EXPAND ALL-NO ARE CHOSEN. --------------------------------------------------------------------------- Report = 1655 Program = FITR.EXE MKT1.0 FITR GIVES INTERNAL ERROR ON MACH210 JEDEC FUSE OUTPUT. --------------------------------------------------------------------------- Report = 1259 Program = INSTALL.EXE MKT1.0 RE-INSTALL THE SOFTWARE & LET IT UPDATE AUTOEXEC FILE FOUND THAT IT GAVE THE PATH FOR PALASM4 AS E:\PALASM AS YOU WOULD EXPECT; HOWEVER, IT GAVE THE PATH FOR ORCAD AS C:\ORCAD. --------------------------------------------------------------------------- Report = 1599 Program = INSTALL.EXE MKT1.0 INSTALLATION IS NOT CREATING A CONFIG.SYS WHEN THERE ISN'T A CONFIG.SYS FILE AND USER SAYS "YES" TO UPDATE CONFIG.SYS. THE SOFTWARE CREATES A CONFIG.M90. --------------------------------------------------------------------------- Report = 1454 Program = JEDPAL.EXE MKT1.0 USING MACH110 JEDEC AND RUNNING THROUGH THE MENU. SELECT RUN/OTHER/DISASSEMBLE FROM/JEDEC GETS ZMALLOC ERROR CODE 86. --------------------------------------------------------------------------- Report = 1469 Program = JEDPAL.EXE MKT1.0 WHEN EXECUTED THE JEDPAL.EXE FOR A MACH110 , THE PROGRAM REPORTED FOLLOWING FATAL ERROR MESSAGES: ZMALLOC:ERROR: CODE86, COUNT = 0008 (0007, 0001) --------------------------------------------------------------------------- Report = 1606 Program = JEDPAL.EXE MKT 1.0 JEDPAL CREATES REGISTERED EQUATIONS ON A 16V8 FILE MODELED AFTER 16L8. THIS FILE WAS A PALASM JED WITH SIM VECTORS APPENDED. --------------------------------------------------------------------------- Report = 1437 OrCAD MACRO LIBRARY MKT1.0 ANOTHER SECONDARY EFFECT OF THE LATCH TRANSPARENT-LOW OPERATION IS THAT WE NEED TO PROVIDE ADDITIONAL NEW MACROS FOR ACTIVE-LOW LATCHES IN OUR LIBRARY. WE CAN NAME THEM ALMOST ANYTHING, BUT I PROPOSE LDX & DLATX. --------------------------------------------------------------------------- Report = 1484 OrCAD MACRO LIBRARY MKT1.0 ORCAD COMPONENT LIB DEFINITIONS FOR TTL MACROS 240,244,245,373,374 (AT LEAST) MUST BE MODIFIED. EACH HAS PINS OF TYPE OUTPUT (RATHER THAT THREE-STATE IN IT'S DEFINITION. --------------------------------------------------------------------------- Report = 1185 Program = MAINMENU 4BETA CHOSING BEGIN NEW DESIGN WITH INPUT FORMAT: TEXT, NEW FILE NAME: ABC.PDS (ANY FILENAME) PRESSING F10 THE SCREEN GOES ALL WHITE WITH CURSOR BLINKING IN MIDDLE. COMPUTER IS LOCKED UP. COMPUADD COMPUTER ONLY. --------------------------------------------------------------------------- Report = 1295 Program = MAINMENU MKT1.0 PRESSING CONTROL C WHILE RUNNING PARSE FROM MENU CAUSES BACKGROUND PROCESS TO TERMINATE BUT DOES NOT RETURN CONTROL TO MENU. --------------------------------------------------------------------------- Report = 1350 Program = MAINMENU MKT1.0 USING DOS 4.0 WITH A LARGE SIZE (1E. > 32K BYTES) THE PALASM 4.0 MENU CONTINUALLY REPORTS THE "OUT OF DISK SPACE" ERROR MESSAGE. --------------------------------------------------------------------------- Report = 1481 Program = MAINMENU Rev1.B MENU PROGRAM DOESN'T CHECK FILE CREATION CHANGES WHEN YOU INVOKE PLDSIM ON RECENTLY EDITED PDS SOURCE FILES. IT SHOULD COMPARE SOURCE MODIFICATION TIME/ DATE AGAINST TRE CREATION & REPARSE WHEN THE SOURCE HAS CHANGED --------------------------------------------------------------------------- Report = 1496 Program = MAINMENU MKT1.0 ATTEMPTING EXERCISE IN INPUT PAIRING, RECEIVED "ERROR F570" PUSHED F3 FOR MORE INFO AND GOT "ERROR RELOADING FROM "XSPAWN" SYSTEM WENT BACK TO DOS PROMPT. THIS HAPPENS IF YOU CHOOSE DIFFERENT DRIVE THAN PALASM. --------------------------------------------------------------------------- Report = 1503 Program = MAINMENU MKT1.0 SHELLING TO DOS ASSUMES COMMAND.COM INSTEAD OF USING THE COMSPEC ENVIRONMENT VARIABLE SO IT FAILS IF THE SHELL IS 4.0 DOS. --------------------------------------------------------------------------- Report = 1506 Program = MAINMENU MKT1.0 HELP HAS THE PATH FOR READER.EXE HARD CODED. IT NEEDS TO BE SET FROM THE ENVIRONMENT. --------------------------------------------------------------------------- Report = 1549 Program = MAINMENU MKT1.0 FITR.PLC IS BEING DELETED BY THE MENU BEFORE INVOKING FITR--IT SHOULDN'T WHEN THE USER HAS SELECTED TO USE PLACEMENT DATA FROM EITHER THE SAVED OR LAST SUCCESSFUL PLACEMENT OPTIONS. --------------------------------------------------------------------------- Report = 1593 Program = MAINMENU MKT1.0 ANY CAPACITY BEYOND THE INITIAL 32 MBYTES ON A DRIVE CANNOT BE USED BY PALASM. "OUT OF DISK SPACE" MSG. APPEARS. SINCE MOST NETWORK DRIVES ARE PARTITIONED TO MORE THAN 32 MBYTES, THIS IS SEVERE LIMITATION TO PROCESS ON NETWORK DRIVE. --------------------------------------------------------------------------- Report = 1596 Program = MAINMENU Rev1.C DOS COMMAND "SP" INVOKES PALASM. --------------------------------------------------------------------------- Report = 1615 Program = MAINMENU MKT1.0 HITTING CONTROL-BREAK (INSTEAD OF ESC) DURING THE COMPILE PROCESS TO STOP EXECUTION WILL LOCK UP PC. SOFT RESET (CTL-ALT-DEL) WILL NOT WORK - KEYBOARD IS LOCKED UP, YOU MUST POWER DOWN. --------------------------------------------------------------------------- Report = 1452 Program = MERGEPDS.EXE MKT1.0 WHEN MERGING THE 23S8, THE SOFTWARE DID NOT RECOGNIZE THE BURIED REGISTERS AS NODES, BUT ASSIGNED THEM AS PINS. --------------------------------------------------------------------------- Report = 1369 Program = MINIMIZE.EXE MKT1.0 MINIMIZE COMPLETES BUT TRE FILE IS CORRUPTED WHEN A SIGNATURE FUSE STATEMENT IS DEFINED FOR A DEVICE NOT SUPPORTING THIS FEATURE. --------------------------------------------------------------------------- Report = 1531 Program = MINIMIZE.EXE MKT1.0 ERROR MSG #3400 IS EXTREMELY CONFUSING. SHOULD LIST SPECIFICALLY WHICH EQN IS ERRONEOUS BY NAME.MSG PLACED BETWEEN TRIVIAL EQNS WHICH CANNOT BE CAUSE. --------------------------------------------------------------------------- Report = 1555 Program = MINIMIZE.EXE MKT1.0 HUNG SYSTEM DURING MINIMIZE WHEN THE LOGIC SYNTHESIS SETUP IS LEFT AT "GATE SPLITTING, MAX=16" AND CHIP TYPE IS MACH 110, ALTHOUGH THIS IS SETUP IS NOT A LEGAL OPTION FOR MACH110. THIS OPTION SHOULD NOT BE ALLOWED OR AN ERROR SHOULD BE FLAGGED. --------------------------------------------------------------------------- Report = 1659 Program = MINIMIZE.EXE MKT1.0 TWO IDENTICAL FILES, ONE NAMED 154-09.PDS AND 154-08.PDS. THE ONE NAMED 154-08.PDS COMPILED AND THE 154-09.PDS DID NOT. --------------------------------------------------------------------------- Report = 1662 Program = MINIMIZE.EXE MKT1.0 A LATCHED OUTPUT FOR MACH110 CAUSES MINIMIZE TO GENERATE AN ERROR, WHICH THEN CAUSES A SYSTEM ERROR 25. --------------------------------------------------------------------------- Report = 1387 Program = PALXPT.EXE MKT1.0 A 20L8 FILE THAT WAS MERGED WITH 16V8 AND HAS FLOATING NODES GOT SYSTEM ERROR 25 INPUT MESSAGE FILE READ ERROR MESSAGE NUMBER IS 4250. --------------------------------------------------------------------------- Report = 1536 Program = PALXPT.EXE MKT1.0 WHEN A PAL (NOT MACH) DESIGN FILE HAS THE PINS FLOATED, FOLLOWING ERROR MSG ACCURED: SYSTEM ERROR 75 INPUT MSG FILE READ ERROR. MSG NUMBER IS 4250. MSG SHOULD INDICATE PINS BE NUMBERED. --------------------------------------------------------------------------- Report = 1542 Program = PALXPT.EXE MKT1.0 29M16 SET (PRESET) & RESET PRODUCT TERMS ARE INCORRECT IN DATABOOK PAGES 2-340 AND 2-341. THE SOFTWARE IS BASED ON THE BOOK. --------------------------------------------------------------------------- Report = 1600 Program = PALXPT.EXE MKT1.0 SEE 23S8.PDS & 23S8.XPT. PIN 13 IS SUPPOSED TO BE COMBINATORIAL. THE FEEDBACK FUSE IN .XPT FILE IS ZERO. THUS WRONG FEEDBACK. --------------------------------------------------------------------------- Report = 188 Program = PARSE.EXE V0.18 DESIGN EXAMPLE WITH 512 SETF/CHECK STATEMENT CRASHES PARSE.EXE OR OUT-OF- MEMORY PROBLEM. --------------------------------------------------------------------------- Report = 1444 Program = PARSE.EXE MKT1.0 PARSE DID NOT CATCH A COMMENT IN THE MIDDLE OF A TRACE_ON STATEMENT. THIS CORRUPTED THE TRE FILE. --------------------------------------------------------------------------- Report = 1538 Program = PARSE.EXE MKT1.0 DESIGN SNP_CNTS.PDS CAUSES THE PARSER TO CRASH, CPU IS HUNG ON 286 COMPAQ, REQUIRED TO REBOOT SYSTEM. ALSO CRASHED ON 386 WITH DOS 4.0. --------------------------------------------------------------------------- Report = 1099 Network = PCNFS 4BETA WHEN TRYING TO VIEW THE FITR REPORT, COULDN'T GO TO THE END OF REPORT, SCROLLING ENDED SOMEWHERE BEFORE THE END OF FILE. THE 2ND LAST LINE WAS TRUNCATED AND LAST LINE WAS APPENDED TO 2ND LAST LINE. USED NFS DRIVER IN MAINMENU. --------------------------------------------------------------------------- Report = 1102 Network = PCNFS 4BETA AFTER MERGING OF TWO DESIGN FILES TRIED TO COMPILE AND GOT ERROR MESSAGE ZMALLOC ERROR. NFS DRIVER WAS IN MEMORY. --------------------------------------------------------------------------- Report = 1182 Network = PCNFS 4BETA WITH PCNFS(V3.0.1) RESIDENT, SCREEN HANDLER HANGS. I CAN STILL ACCESS DOS, BUT THE PALASM SCREEN DOES NOT CHANGE. MANIFESTS ONLY WHEN PCNFS IS RESIDENT. ENTER PALASM4. SELECT [VIEW] [WAVEFORM]; [TRACE], <ESC> - SCREEN HANGS. --------------------------------------------------------------------------- Report = 1204 Network = PCNFS 4BETA DURING PARSE ERROR OCCURRED. MESSAGE - SYSTEM - ERROR P103. OUT OF SYSTEM MEMORY. THE ONLY OPERATION PERFORMED BEFORE THIS WAS A SIMPLE EDIT. NFS DRIVER WAS PRESET. REPEATED COMPILE -NO ERRORS. --------------------------------------------------------------------------- Report = 1634 Program = PINOUT.EXE MKT1.0 PINOUT DOES NOT WORK ON 29M16'S PALASM4 V1.0 USING "TAXI.PDS" IN THE EXAMPLES DIRECTORY. --------------------------------------------------------------------------- Report = 1560 Program = PL2PDS.EXE MKT1.0 PALASM4 FINDS PLPL BUGS. IN ONE 22V10 DESIGN THERE WAS A CASE OF A MISSING PARANTHESIS. THIS BUG RESULTED IN NO ERRORS IN PLPL, BUT WAS CAUGHT AS A SYNTAX ERROR (WHICH IT IS) BY PALASM4. --------------------------------------------------------------------------- Report = 1561 Program = PL2PDS.EXE MKT1.0 INABILITY OF PL2PDS TO HANDLE THE IF-THEN-ELSE CONSTRUCT CORRECTLY. --------------------------------------------------------------------------- Report = 1562 Program = PL2PDS.EXE MKT1.0 INABILITY OF PL2PDS TO HANDLE CASE STATEMENTS CORRECTLY WHEN THEY ARE EMBEDDED INSIDE OF IF-THEN-ELSE CONTRUCTS. --------------------------------------------------------------------------- Report = 1564 Program = PL2PDS.EXE MKT1.0 STACK OVERFLOW WHILE TRYING TO COMPILE A 22V10 DESIGN. --------------------------------------------------------------------------- Report = 1518 Program = PLCBAK.EXE Rev1.B FILE HAS MULTIPLE PINS/NODES ON ONE LINE:- NODE ? A_TWN PAIR A_PAO PIN 3 A_PAO THIS SYNTAX IS LEGAL TO PARSE BUT PLCBAK SKIPS MULTIPLE PINS/NODES LOCATED ON ONE LINE. --------------------------------------------------------------------------- Report = 1306 Program - PLDSIM.EXE MKT1.0 SIMULATOR SHOULD RECOGNIZE BLOCKS FOR SETF & RSTF EQUATIONS ON MACH110. --------------------------------------------------------------------------- Report = 1314 Program - PLDSIM.EXE MKT1.0 SIMULATOR ERRORS ON VECTOR5 PINS O17 & O26. PLDSIM SENDS 2 CONDITION WHEN IT SHOULD BE X. --------------------------------------------------------------------------- Report = 1316 Program - PLDSIM.EXE MKT1.0 PATTERNS FT003 & FT004 FAIL DEVICE PROGRAMMER VERIFICATION BECAUSE THEY DO NOT HAVE EITHER A RESET OR PRESET CONDITION AS PART OF THE FIRST JDC FILE VECTOR. --------------------------------------------------------------------------- Report = 1479 Program - PLDSIM.EXE Rev1.B SAMPLE FILE X.PDS HAS NUMEROUS CLOCK EVENTS CREATED BY CLOCKF STATEMENTS, BUT THE OUTPUT HISTORY FILE HAS SIGNALS CLK1 & CLK2 STUCK LOW FOR ALL OF THEM. THIS IS WRONG THEY SHOULD GO L/H/L FOR EACH CLOCKF STATEMENTS. --------------------------------------------------------------------------- Report = 1519 Program - PLDSIM.EXE Rev1.B PLDSIM PLACES A "H" IN JEDEC FILE WHERE A "1" SHOULD BE FOR OUTPUTS THAT WERE TRI-STATED IN A MACH110 DESIGN. --------------------------------------------------------------------------- Report = 1528 Program - PLDSIM.EXE MKT1.0 FILE WORDCNT SUBMITTED BY CUSTOMER INCORRECTLY PRODUCES ERROR: "CANNOT SETF" AN IOPIN". --------------------------------------------------------------------------- Report = 1540 Program - PLDSIM.EXE MKT1.0 REG ATTRIBUTE IS DECLARED FOR PIN 6 IFFERR.ALSO A TRISTATE EQN IS DECLARED IFFERR.TRST=VCC. A REGULAR REGISTER EQN & FUSES S0 & S1 SHOULD BE 0 OR DEFAULT TO COMBINATORIAL/ACTIVE LOW WHICH IS 1. PLDSIM TREATS THIS AS A REGISTER. --------------------------------------------------------------------------- Report = 1601 Program - PLDSIM.EXE MKT1.0 SIMULATION IS INCORRECT ON 16V8 FILE WITH OE PIN POLARITY. --------------------------------------------------------------------------- Report = 1675 Program - PLDSIM.EXE MKT1.0 USING CE610 FILE, LHLDA IS STUCK HIGH WHILE BEING RESET. VECTORS DIDN'T VERIFY ON PROGRAMMER. --------------------------------------------------------------------------- Report = 1183 SYSTEM Problems 4BETA I TRIED TO LOOK AT HELP ON ERRORS IN THE DOCUMENTATION SECTION. THE MENU BLINKS "LOADING...HELP ON ERRORS". THERE IS NO DISK ACTIVITY. RETURN & ESC ARE IGNORED. THE MACHINE IS HANG.COMPAQ 286 PORTABLE. --------------------------------------------------------------------------- Report = 1515 Program = TREPL2.EXE Rev1.B ERROR T9011 INVALID OR CORRPUT TRE FILE ONLY OCCURS WHEN EXTENDED MEMORY SW INSTALLED. --------------------------------------------------------------------------- Report = 1566 Program = TREPL2.EXE Rev1.B DISSASSEMBLE FROM INTERMEDIATE FILE FAILED WITH THE MSG: "INVALID TRE FILE" THIS HAPPENED ON ALL DESIGNS. --------------------------------------------------------------------------- Report = 1355 Program = WAVE.EXE MKT1.0 WHEN PRINTING, DOESN'T PUT WAVEFORMS ON SAME PAGE AS PIN NAMES. --------------------------------------------------------------------------- Report = 1356 Program = WAVE.EXE MKT1.0 CHECK CLASH ON LAST VECTOR DOESN'T PUT ? INTO HISTORY OR TRACE FILES. THIS WAVEFORM LOOK OK, BUT RUNTIME LOG SAYS ERROR. --------------------------------------------------------------------------- Report = 1410 Program = WAVE.EXE MKT1.0 SIMULATION WAVEFORM DID NOT PRINT RIGHT DID THE FF: VIEW, TRACE & I SEE IT TO PRINT:F2, PRINTER, HP/LASERJET II, RUN THE PRINTER NOW PRINTS PAGES OF JUNK. I TRIED BREAK, & CTL C & WAS ABLE TO ABORT THE TIME BEFORE THIS MACHINE WAS HANG.