Windows ME
#2
Posted 09 April 2000 - 04:40 AM
#3
Posted 09 April 2000 - 11:18 AM
[This message has been edited by tylau (edited 10 April 2000).]
#4
Posted 10 April 2000 - 01:50 AM
#5
Posted 11 April 2000 - 05:05 AM
Someone would ask me what system do ya have...?
In a manly voice:
1Ghz P IV
1GB of RAM
A 75GB Hardisk
A GeForce DDAAMMFFAASSTT Video Card
And what OS?
In a teenage breaking voice I would have to reply:
MEeeeEEeeeeeEEEEeeee.
WTF, Gay GAY GGGAAAAYYYY. Heh
#6
Posted 11 April 2000 - 06:39 AM
#7
Posted 11 April 2000 - 08:56 AM
#8
Posted 12 April 2000 - 03:26 AM
I let my mouth (or fingers in this case) go to far sometimes - didn't mean to offend anyone.
I've just been an NT person since day one. Haven't crashed since the day I put 2k on my machine, and have only rebooted to update Nvidia drivers and such... Stress freeeee computing ... ahhhhhhhh
#9
Posted 12 April 2000 - 09:24 AM
#10
Posted 12 April 2000 - 10:35 PM
Get real, MS has every right to charge for this product. It may not be exactly what you want but lets face it pal, your not Boeing or some other HUGE customer so your one voice doesnt count for a whole lot. If you don't like it don't buy it, no big deal for MS.
#14
Posted 13 April 2000 - 11:19 PM
#15
Posted 14 April 2000 - 04:12 AM
MSGUY, (and I hope not to offend you with this. Just my opinions) there are a few reasons for why I wont consider buying Windows Me (sorry, but that name just is to irritating. Falcon, eagle, monster, something else other than Me). One is once again that tight integration of the browser/active desktop that just eats up resources and slows things down. Hopefully, another version of 98Lite for Win ME that will fix that problem. You would think after the Anti-trust trial, this feature would be removed (making the OS a whole lot faster).
Another is that Win2k Pro is such a much better choice, utilizing NTFS security and incredible stability.
Microsoft is at it once again by removing support for other NOS systems such as Novell and Banyan (to force people to use Win2k pro, which is costly to the small business world. And to somehow make people use the Active Directory services instead of NDS of Novell).
Another good reason is the availabilty of alternative OS's out there, most of them free.
For me, Win95 still has not outgrown my needs (I just wish it would stop crashing once every so often). Win2k and Red Hat fill the gaps that win95 doesnt cover.
I do agree with you that the programmers at microsoft should get paid for their work, but not for buggy software. But one features of windows 98 was to download any updates. If win Me is really nothing more than an update to win98, why are we still paying for a whole new upgrade?
If Microsoft was to change the name into something more "ballsy" and was to remove the active desktop/web intergration to speed up the OS, I would actually consider buying this product. But for now, I dont see myself wanting a slower OS that win2k pro can easily replace.
------------------
Celeron 300A@450, Abit BH6, 160 RAM, Seagate Barracuda 20.4gig 7.2k rpm UDMA66, Modified Promise ultra66 turned into a Fasttrack hack, 48x Lite-on CDROM
Diamond v770 tnt2 16 meg, Voodoo2 8, meg, 17"Daytek
#16
Posted 14 April 2000 - 06:49 AM
#17
Posted 14 April 2000 - 01:50 PM
I actually see no point in ME. If I'm not going to use dos, then I'll use win2k. If I need dos/backwards compatibility that win2k doesn't offer I'll use 98. ME can't be used, and that means it's totally useless for my purposes.
#18
Posted 14 April 2000 - 10:11 PM
lol
Thanks..
and I was acually looking for a LEGAL place to get ME...
/me slaps self with a trout for being so stupid
#19
Posted 14 April 2000 - 11:55 PM
I think its funny that people beleive the myth about bug free software. In the end no software is bug free. There are just too many people trying to integrate too many things for there not to be some gaps where this don't mesh perfectly. Drivers are the perfect example. Driver installers are constantly updating dll's. This works fine if you're using a standard install of the OS, but what happens if you have an older driver which already updated that dll? The newer version of the dll may not contain the APIs that the older driver relied on to work correctly which causes the older driver to begin to fail/BC/bsod...
#20
Posted 15 April 2000 - 05:57 AM

Help










