Groups | Search | Server Info | Login | Register
Groups > comp.os.ms-windows.misc > #781
| From | Daniel65 <daniel47@nomail.afraid.org> |
|---|---|
| Newsgroups | comp.os.ms-windows.misc, alt.comp.os.windows-xp, alt.windows7.general, microsoft.public.windowsxp.general |
| Subject | Re: Windows 32-bit |
| Date | 2024-01-01 21:04 +1100 |
| Organization | A noiseless patient Spider |
| Message-ID | <umu2nv$263h5$1@dont-email.me> (permalink) |
| References | (6 earlier) <AvORUBn4jxjlFwEZ@255soft.uk> <3fj0pi1he28cfgbul4lbmu4jua526btugq@4ax.com> <$93+An1C1HklFwbp@255soft.uk> <umrm4d$1nhbb$2@dont-email.me> <t+aKQ8$3BWklFwIa@255soft.uk> |
Cross-posted to 4 groups.
J. P. Gilliver wrote on 31/12/23 11:37 pm: > In message <umrm4d$1nhbb$2@dont-email.me> at Sun, 31 Dec 2023 > 23:17:19, Daniel65 <daniel47@nomail.afraid.org> writes >> J. P. Gilliver wrote on 31/12/23 7:27 am: >>> In message <3fj0pi1he28cfgbul4lbmu4jua526btugq@4ax.com> at Sat, >>> 30 Dec 2023 12:10:57, Tim Slattery <TimSlattery@utexas.edu> >>> writes >>>> "J. P. Gilliver" <G6JPG@255soft.uk> wrote: >>>> >>>>> For 386 and 486, the confusingly changed what "SX" and "DX" >>>>> meant; on one (I forget which), SX meant it _didn't_ have a >>>>> floating-point maths co-processor on board, DX meant it did. >>>>> On the other, SX meant it had a half-width (so 16?) bus >>>>> outside the chip (so requiring two fetches to >>>> The 486 was the first Intel chip to have the numeric >>>> coprocessor onboard. Intel wanted to prese4ve the "SX" price >>>> point, so they produced a 486SX chip which was identical to the >>>> DX except that the numeric coprocessor was disabled! Machines >>>> sold with this chip had an empty socket where you could plug in >>>> a 486DX chip to get a coproc. So once you did that, you could >>>> unplug the SX chip and use it elsewhere, right? WRONG!!! It was >>>> set up so that the DX in those machines wouldn't work unless >>>> the SX was plugged in, doing nothing. >>>> >>> Did anyone ever manage to "crack" the 486SX or the 487 to enable >>> the disabled part, or make it work without the other? >> >> "487"?? All DuckDuckGo shows seems to concern a Californian Penal >> Code clause 487!! ;-P > > Maybe it was 486DX as Tim says. I had _thought_ the '387 was the > co-processor for that series. > > I'm not sure when they started to drop the "80" from (e. g.) 80386. I > know they started using names around the time of the '586, alias > Pentium, because someone in charge of the administration of > trademarks said, basically, no more trademarking just numbers. (It > wasn't just Intel - other manufacturers had to invent names too; I > remember one chip called "roboclock"; I think it was Maxim or IDT.) > Presumably that's why things moved to Pentium II, etc., rather than > 686. (Rumour-mung Rumour-mung) The story I was told, way-back-when, was that in an effort to wipe out Apple and Commodore, etc, Intel virtually gave anybody the Rites and the Chip designs to produce the 80186, 80286, 80386 and 80486 Chips. Then, having effectively achieved their Aim, when Intel produced the 80586, a.k.a. the Pentium chip, IBM required Royalties-type stuff (shut the gate), so some manufactures (AMD, etc.) continued development independently, to produce the 586 and 686 chips. It may have also been the case that, as seperate companies were doing their own development, some 586/686 chips had different pin-outs and/or Op-Codes to other 586/686 chips!! Something like that. -- Daniel
Back to comp.os.ms-windows.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-17 15:02 +0200
Re: Windows 32-bit Marco Moock <mm+usenet-es@dorfdsl.de> - 2023-11-17 14:06 +0100
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-11-17 11:37 -0600
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-17 18:04 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-18 19:28 +1100
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-18 10:13 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-18 22:49 +1100
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-18 13:28 -0600
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-19 08:55 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-19 23:01 +1100
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-19 12:58 +0000
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-11-19 10:44 -0600
Re: Windows 32-bit Bob F <bobnospam@gmail.com> - 2023-11-19 11:32 -0800
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-19 21:38 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-20 20:40 +1100
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-20 10:07 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-21 00:26 +1100
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-20 14:11 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-21 20:20 +1100
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-21 10:08 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-21 23:15 +1100
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-20 18:23 +0000
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-20 23:00 -0600
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-21 10:12 +0000
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-21 20:59 -0600
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-22 05:02 +0000
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-22 02:38 -0600
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-22 10:11 +0000
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-22 23:08 -0600
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-22 10:28 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-22 10:12 -0500
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-21 20:22 +1100
Re: Windows 32-bit Char Jackson <none@none.invalid> - 2023-11-20 14:45 -0600
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-11-18 11:37 -0600
Re: Windows 32-bit Zaidy036 <Zaidy036@air.isp.spam> - 2023-11-18 15:00 -0500
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2023-11-18 20:38 +0000
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-19 08:57 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-11-19 20:00 +1100
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-11-19 10:47 -0600
Re: Windows 32-bit Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-11-18 13:10 -0800
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-19 09:00 +0000
Re: Windows 32-bit Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-11-19 13:45 -0800
Re: Windows 32-bit John Hall <john_nospam@jhall.co.uk> - 2023-11-20 08:46 +0000
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-19 06:12 +0200
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-11-19 10:54 -0600
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-17 13:36 +0000
Re: Windows 32-bit GlowingBlueMist <zapbot@truely.invalid> - 2023-11-17 09:05 -0600
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-19 06:43 +0200
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 11:28 -0500
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2023-11-17 16:16 +0000
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-19 07:01 +0200
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2023-11-19 19:34 +0000
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-12-29 09:49 +0200
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2023-12-29 15:27 +0000
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-29 19:07 +0000
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2023-12-29 19:56 +0000
Re: Windows 32-bit Tim Slattery <TimSlattery@utexas.edu> - 2023-12-30 12:10 -0500
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-30 20:27 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-12-30 23:14 -0500
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-31 05:12 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2023-12-31 23:17 +1100
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-31 12:37 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-12-31 11:35 -0500
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-31 19:15 +0000
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-12-31 14:43 -0600
Re: Windows 32-bit Frank Slootweg <this@ddress.is.invalid> - 2024-01-01 11:25 +0000
Re: Windows 32-bit Daniel65 <daniel47@nomail.afraid.org> - 2024-01-01 21:04 +1100
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-12-31 14:39 -0600
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-12-31 22:11 -0500
Re: Windows 32-bit Tim Slattery <TimSlattery@utexas.edu> - 2023-12-29 11:31 -0500
Re: Windows 32-bit "Kerr-Mudd, John" <admin@127.0.0.1> - 2024-01-02 13:22 +0000
Re: Windows 32-bit Ralph Fox <-rf-nz-@-.invalid> - 2023-11-18 06:56 +1300
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-19 07:07 +0200
Re: Windows 32-bit Ralph Fox <-rf-nz-@-.invalid> - 2023-11-19 21:07 +1300
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 13:52 -0500
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-12-29 09:54 +0200
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-18 06:53 -0500
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-11-19 07:41 +0200
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 03:17 -0500
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-19 16:57 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 13:57 -0500
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 14:21 -0500
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-19 21:22 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-11-19 17:56 -0500
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-19 23:59 +0000
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-20 12:45 +0000
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-20 15:19 +0000
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2024-06-07 00:39 +0100
Re: Windows 32-bit "Auric__" <not.my.real@email.address> - 2024-06-07 14:50 +0000
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2024-06-07 11:33 -0400
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2024-06-07 16:50 +0100
Re: Windows 32-bit "Auric__" <not.my.real@email.address> - 2024-06-08 16:34 +0000
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2024-06-08 18:09 +0100
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2024-06-09 19:03 -0400
Re: Windows 32-bit "Auric__" <not.my.real@email.address> - 2024-06-11 06:16 +0000
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-12-29 09:59 +0200
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-11-19 13:32 +0000
Re: Windows 32-bit Java Jive <java@evij.com.invalid> - 2023-11-19 13:59 +0000
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2023-12-29 10:07 +0200
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-12-29 04:21 -0500
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-29 11:56 +0000
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-12-29 12:26 -0600
Re: Windows 32-bit Paul <nospam@needed.invalid> - 2023-12-29 22:38 -0500
Re: Windows 32-bit "J. P. Gilliver" <G6JPG@255soft.uk> - 2023-12-30 08:30 +0000
Re: Windows 32-bit Mark Lloyd <not.email@all.invalid> - 2023-12-30 15:26 -0600
Re: Windows 32-bit Steve Hayes <hayesstw@telkomsa.net> - 2024-01-04 17:48 +0200
csiph-web