please explain. i'm all ears.

(all drivers for 64 had to be re-provide or die, network cards included: nic cards are 48 bit. this isn't the only "it's full of shit" indicator, the nic is just one example that what they said they were doing with 64 is a big lie)

millenials please answer

Is that you need to stop being such a fucking ass pie and go to your hugbox.

http://www.fairfaxunderground.com/forum/read/40/3164222.html

(Windows 10, Apple, and UBUNTU all required that users switch to 64 or die (32bit "despreciated", not available, no new hardware supports it right), all drivers for all hardware MUST BE 64, meaning if your hardware maker is from china and doesn't see profit in re-writing your driver: your equipment ceases to operate)


all hardware drivers for all hardware (video card, sound card, etc) MUST BE 64 bit. but 32bit hardware drivers upgrades will NEVER BE PROVIDED*

such as sound support for Dell laptops: gone, no sound in Win10 ever again - and everyone knows linux sound support went from difficult to, after Bill Clinton, plain awful - perhaps intentionally awful to get rid of anyone not in the inner circle, would be a reasonable accusation with no other proofs appearing

(note to stupid millenials: hardware support is the core of a PURCHASING audience and the vexation of a something like freebsd trying to stay "pure" (compatible, able, unix). getting a 32bit base that supported hardware then to have allot of it deleted? a travesty: that many insiders incl ubuntu people helped insure got pushed down the pipe)

"you need a 64 bit driver for a 48bit card that worked on a 32bit computer?"


this shows the whole thing off to be a BIG LIE. it can't be explained because mr. 64 bit upgrade is a total lie.

"32bit" had AGP bus

what was that? not 32. so if it wasn't 32 and 64 is an upgrade, how is 64 to 64 an upgrade if it wasn't 32 ??

well my 64 PC says it accepts 32bit cards

IT DOES NOT. that's called a lie in advertising.

a few trivial are supported but THE MAIN ONES - sound and video - ARE NOT

they are NOT in two ways:

(1) no sound at all

(2) new video driver has most features removed if you even GOT ONE


this one is extremely important

(3) new 64 card says VESA (which would say it works 32 OS), BUT IT DOES NOT, infact it has no VESA at all in it - only the label remains

this means DRIVER SUPPORT isn't the only thing that was attacked in the mr. 64 bit "forced upgrade"

64bit means "the older 32bit OS is not allowed to run on anything, because PCIe will refuse to talk if it is asked a PCI question"


it's not just about 32 accepting 64 (which it already had !!): it's about 64 refusing 32 with no documentation or apology.

it's not just about 32 accepting 64 (which it already had !!): it's about 64 refusing 32 with no documentation or apology.

means the 32bit sound cannot work with Windows10 because they planned it to dies

means the 64bit (say video) cannot work with "a linux that didn't upgrade to 64" because the actual electronics lies on the box - it says it supports it does not and infact if that cards is asked in PCI language - it returns that the operations are refused

IT REFUSES TO WORK, IS WHY

you need a 64 bit driver for a 48bit card that worked on a 32bit computer?

but a 64bit card is NOT ALLOWED to talk to talk to the 32bit software ?

that's right. that's what they planned and that's how it is.

It's because a 48bit is 12bit chunks.

Techie O Wrote:
-------------------------------------------------------
> It's because a 48bit is 12bit chunks.

and they aren't "chunks" and they aren't taken 12bit at a time either

then why did it work with 32bit dumb ass?

stop insulting people's intelligience with YOUR FAKE ANSWERS

well i guess i have to accept it, because BIG IT gets everything they want and gets paid big to want it

i'm just a "customer"

Microsoft Bob was the greatest OS ever written.

little red riding hood

.

reconfigure your CMOS

Windows Vista, yay!

Windows Vista Wrote:
-------------------------------------------------------
> Windows Vista, yay!

pci-e support in the kernel could lock out all drivers - to force upgrades - IT COULD ALSO have an n-bit interface: it could do either

it would be a dirty low down trick to immediately not support anything except 64bit - yet it was done by windows and linux WITHOUT even a discussion or debate

64 was planned from the beginning to knock out small systems and old hardware

u need 2 Wrote:
-------------------------------------------------------
> reconfigure your CMOS

DROP DEAD G2, THAT DOES NOT MAKE OLD HARDWARE WORK IN WINDOWS OR LINUX

there is not one article referencing that cmos would do that or that windows allows the end user to edit cmos either.

ALSO: CMOS is no longer installed in any modern pc - meaning the older style BIOS which u need 2 improperly has confused

(he doesn't even know the name for bios - don't believe a word he says)

finally: chips today are very hacky - feature wise - they add and remove features and software that supports a feature later becomes "SCREWED" when the feature changes or gets removed. many things are in today's chips that aren't released to street urchins. more than ever even today's chips are designed to lock out and confuse small competition. (you cannot compete with many things because half the code is in the chip, and that part is never released to the public in a usable manner or at all). they are hacking in silicon these days.

8 bits of silver!

d

This is going to sound ironic since I'm posting it on an online forum, but I hate computers. Too complicated, not user friendly, you buy piece of hardware/software and it's obsolete an hour later. I'm only 30, but I get why boomers prefer type writers.

64 bit is the cat's ass. it only helps lazy "unreal tournament engine" programmers and only via craddling their laziness. and what about 100bit busses back in the 1980's? what about VR that will demand 100bit?

Intel and AMD chips already had 64bit support before the "64 changeover" where all 32 devices were "oh, you must buy new devices from china"


64bit isn't a "new cappability" it was merely a bithack "new default". all those chips had 64bit instructions accessible to 32bit programs !!


now it's the CORRUPT REVERSE, you have 64bit programs accessing 32bit - same fucking thing

oh and btw how many bits at a time did the bus copy? varies. none of your business anyhow

also 3D video cards, they were using 64 even 128 bit - the software worked fine and usually the "game engines" used 64bit Intel AMD instructions for dealing with them


a bithack "default change" that caused a trillion dollars in damages the BIG TECH all colluded for

big tech - they always do things that cause "precious time" to be lost

they don't loose much and have developers who are paid - everyone else take a bath when precious time is wasted by "wide sweeping senseless platform changes"

now if i told you "ok 64 means all the 32 instructions are gone" that would mean something (fewer instructoins, more cores per chip, all 64)

BUT THAT IS NOT THE CASE

1 bit and character, 16, 32 are all still supported

therefore: only the default was changed, nothing else

it was a fucking bithack that intently cause CONSUMERS allot of money - and tilted things toward chinese sales

many "honest programmers" were against the change. infact not all at Intel liked it

infact - anything 64 can be done 32 (anything 128 can be done at 32). Intel made multi-core chips after the release of 64, a 32 multi-core, to prove that if you DO NOT GO 64, you get ALLOT MORE CORES

the media and big tech completely ignored the news - and big tech all colluded to "OUR OPERATING SYSTEM SUPPORTS 64 ONLY", which was a total fraud (32bit hardware could easily be supported: it was the chineses who reused to allow that to happen specifically. strong arm tactics). (as i told you, 32bit is absolutely supported in the "all 64" i was never all 64 that's a damn lie)

"well, wikipedia says 64bit means more memory can be accessed, 32b had the 4G limit - many pc use 8G and above now"

no, 32bit had no such limit because there were 64bit instructions and registers before the switch as i've said many times

IT'S A LIE THOUGH, because 32bit programs run in a 64 system (with their hardware deleted, as i chinese discussed above). while the OS needs 64 bits programs do not (and the ones that do? 64bit is still a crutch and work-around)

when a program runs the OS doesn't give it 64bit adressed memory "automatically", doesn't work that way. never worked that way

memory is by segment and offset and the reason is that software MUST be shielded from knowing "real mode details" such as how and when it's been re-located

saying 64 bit doesn't need shielding but 32bit did would represent a total lack of knowlege of what goes on. what goes on is "everybody is real mode" sets up the system for a total IT tech failure


if you have a 32bit segment and 32bit offset, that's 64bit ALREADY, already had 64bit OS memory access

efficiency: it's efficient if not more efficient* to access terabyte range data by segment and offset - it's 4G per rip. this is as opposed to specifying a 64bit range. the difference is ZERO, i hope you understand.


* you must understand that the "64 default" platforming OS hack is not the default inside the memory chips, which use many schemes to access data NOT IN REAL MODE (that's the meaning of "DRAM" as opposed to "STATIC RAM")

"what about 64bit copying, that's rips right" ? NO, THAT'S A WIKIPDEDIA LIE

motherboards (such as 100% all Intel boards) have varied support for varied types dram and sram and other modules

the upshot of this is "it's none of programmer's business and far outside the control of the OS and programs" to decide how memory is transferred efficiently: that's all done by triggered circuitry working in protocols not even in the OS language. it could be 8 at a time but 128 wide, it could be 32 at a time 48 wide and it's "none of your business"

all you know is your board supports the DRAM DIMM module you bought or it does not

many "honest programmers" were against the change. infact not all at Intel liked it

infact - anything 64 can be done 32 (anything 128 can be done at 32)

Intel made multi-core chips after the release of 64, a 32 multi-core, to prove that if you DO NOT GO 64, you get ALLOT MORE CORES. the demo core had n times the cores of the 64bit intel chips and absolutely kicked the performance of 64 out the door*

* for properly multi-threaded applications and OSes

the media and big tech completely ignored the news - and big tech all colluded to "OUR OPERATING SYSTEM SUPPORTS 64 ONLY", which was a total fraud (32bit hardware could easily be supported: it was the chineses who reused to allow that to happen specifically. strong arm tactics). (as i told you, 32bit is absolutely supported in the "all 64" i was never all 64 that's a damn lie)

another fact is all the work (segmenting 1T range "non-real mode software support", variable precision numbers much greater than 64bit needed by math applications, wide graphics on non-wide cpu or bus and vice-versa, ALL OF IT, even interfaces that had "no native bit-ness" (where bit-ness was merely an option))

(yes that's right - 64bit isn't nearly large enough for common math, arbitrary precision is needed even for simple calculations - don't look that up on wikipedia they LIE, 64bit can't represent many simple fractions - plain fact)

all the work was already done. 64 default switch only funded #hillary hackers to change the work that was already done by senselessly and irresponsibly bit-hacking. all that done work is still needed and in use in 64 platforms - difference? consumers were attack, hardware was force-upgraded, china made out BIG

hell no 64 isn't enough. it's nowhere near enough for common math (again: WIKIPEDIA LIES, 64 does NOT support large numbers under division, 64 is a 2yr old doing math for DIVISION)

so if many have 1T drives and you back them up, say your a storage facility. so you could cloud 18,500 customers tops

but customers are now getting 5T drives, so that's 3,500 customers served

64 is big? my ass 64 is big

what's big is progress, and 64 reaks of china, lost time, and lies

with TWICE THE NUMBER OF CORES, the 32bit platform far outperforms 64 in every which way

(if copying 4G at a time was too slow it's wouldn't be: but the fact is copying 4G at a time still chokes most drives, memory, and cpu for ? an hour? minutes? it's not even remotely close to being considered too small)

now, if you said "8bit core", millions of cpu cores that might get interesting, since the frequency of copying 256 bytes at a time and having to re-issue the instructoin, despite having 8x the number of cores, might be a game changer. might. 4G at a time? absolutely no problem. 4G is still not a consideration in the microsecond millisecond arena and won't be perhaps ever.

DID ANYONE THINK 32 WAS CHOSEN FOR NO REASON? 32 helped crippled software before certain OS problems were solved - but those problems - they were solved in the 80's and 90's 10 times over

ALSO - WHEN 32 was introduced people were not asked to throw away their 16bit hardware

REPEAT - WHEN x86 32 replaced x86 16 - PC hardware was more often made in usa (using some foreign parts) AND SUPPORTED, NOT THROWN AWAY

but even 4G at a time is "a white lie" because if that were limiting (it certainly is not, it is mathematically zero sum game)

a PC chip or software could tell a bus "hey, that disk, dump it in one of 4 billion memory banks of 4G each fast and don't fucking tell me how many bits it is, don't tell me it's total size i don't care"

it could have another agreement with bus to do a 4 billion bank fills at once

you see: 64bit default doesn't mean shit. it is only a harassment upon small tech and a huge bonus for chinese manufacturers and lack of any legal support for small tech

^^ you might think the above is fanciful - i guarantee you some of the SSE Intel extensions (and ARM hacks) are designed to do exaclty "that kind of thing" - to talk to the bus about doing some "non-real mode" work

Sven, take your medication.

A 32 bit card can be supported on 64 and 128 or whatever CPUs. The bus width doesn't matter. PCIe is 1, 4, 8 or 16 (I think the latest spec allows 32x too) bits wide. The problem is that the card can only address 32 bits of physical memory. If you allocate your device somewhere above the 32 bit line, which is common is 64 bit systems, the device can't read/write to it. There are some ways around this. Allocate your device memory below the 32 bit line. That requires operating system support. Use an address translator. The Mac had hardware called the DART which could do the translations. It's possible some IOMMUs can do it as well. Regardless, no one apparently wrote a glue layer to handle all this transparently so someone needs to modify and rebuild the driver.

Gosh why everybody on this forum advises to change medication? Are you goddamn nuts? Of course the drivers for 64x operating system will not work with 32x system! Downloading correct driver is forbidden by your moral principles or what? Thank God I never have this kind of problems as I use Mac plus macflypro.com that protects the data from all unwanted files and other security issues. I think you should use Mac computer too. There are never any silly issues there. You will never have a multi-page discussion on such a simple thing!

Have you tried using your pitching wedge as a driver?

j4u7y Wrote:
-------------------------------------------------------

> A 32 bit card can be supported on 64 and 128 or
> whatever CPUs. The bus width doesn't matter. PCIe
> is 1, 4, 8 or 16 (I think the latest spec allows
> 32x too) bits wide. The problem is that the card
> can only addres

we are not talking about can be. IT WAS NOT AND STILL IS NOT. the post clearly says they deleted hardware support intently. the post also accuses them of intently damaging the systems so that the same would occur - and also that china is the benefactor (as well as big tech in general)

FUCK OFF AND DIE g2 GERRYMANDERER2

YOU KNOW DAMN WELL WINDOWS 10 KILLED SUPPORT FOR PRINTERS AND USB THAT HAD 32-BIT DRIVERS - ALSO COUNTLESS VIDEO CARDS AND OTHER HARDWARE

AND SO DID UBUNTU

it was designed and planed by "big tech" to force consumers to buy new hardware FOR ABSOLUTELY NO REASON

-------------------------

DROP DEAD G2 GERRYMANDERER2. YOU'VE POSTING SUICIDE ESSAYS, MUTILATED BODIES, CHILD PORN, DEMOCRAT AGENDAS, ANTI-TRUMP POSTS, ANYTING ANTI-AMERICAN FOR 10 YEARS AND COUNTING

FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2


FUCK OFF AND DIE g2 GERRYMANDERER2