Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. People who complain about Microsoft are like...

People who complain about Microsoft are like...

Scheduled Pinned Locked Moved The Lounge
csharphardwaretutorialquestiondiscussion
36 Posts 15 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    David Wulff
    wrote on last edited by
    #1

    Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


    Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

    G M S T A 6 Replies Last reply
    0
    • D David Wulff

      Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


      Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

      G Offline
      G Offline
      George
      wrote on last edited by
      #2

      I will only focus on the rebooting - it is true that companies are regularly rebooting the windows based servers to ensure proper operation. I think it is once a week or so - and it seems to be the recommended by M$ procedure actually.

      A T 2 Replies Last reply
      0
      • D David Wulff

        Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


        Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

        M Offline
        M Offline
        Michael Dunn
        wrote on last edited by
        #3

        Linux zealots never let the facts get in the way of a good religious war. ;) --Mike-- http://home.inreach.com/mdunn/ You are the weakest link, GOODBYE!

        R R 2 Replies Last reply
        0
        • M Michael Dunn

          Linux zealots never let the facts get in the way of a good religious war. ;) --Mike-- http://home.inreach.com/mdunn/ You are the weakest link, GOODBYE!

          R Offline
          R Offline
          Robert Dickenson
          wrote on last edited by
          #4

          You say that as if a Windows/Microsoft zealot doesn't do exactly the same thing. X| Robert.

          M 1 Reply Last reply
          0
          • R Robert Dickenson

            You say that as if a Windows/Microsoft zealot doesn't do exactly the same thing. X| Robert.

            M Offline
            M Offline
            Michael Dunn
            wrote on last edited by
            #5

            It's been my experience that among the general net population (ie, those that post in public message boards) no one gets their panties in a bunch like Linux and anti-MS zealots do. It's like they just can't sleep at night knowing there's someone on the planet who hasn't been enlightened and gone over to the light side of Linux. Conversely, people who use only Windows don't care about Linux. So there are no MS zealots. Again, in my experience. --Mike-- http://home.inreach.com/mdunn/ You are the weakest link, GOODBYE!

            D 1 Reply Last reply
            0
            • D David Wulff

              Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


              Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

              S Offline
              S Offline
              Sardaukar
              wrote on last edited by
              #6

              ...since our servers, for example, are alive and running (with an exception, thanks to electric power company :( ) from 5? 6 months? True, there were seevral restarts (but that's because some patches and upgrades were applied and Windows requires restart. This is, indeed, unpleasant, but is something else). And these servers hosts SQL Servers, IIS, Exchange, Terminal Server, schedulers, printers - that means everything you need for a Windows NT/2000 server to get into trouble :)... And that's not all. Also some guys from our company - not me, of course :) - are testing NT services, network managers, IP tracers, remote system editing tools, user and printers manager, desktop switchers, an economical software - which is not big, but it has several thousands windows inside :) - , all of us perform huge print jobs etc. etc. etc. (Let's not forget the Starcraft combats during work time). Also, we have here Windows 2000 workstations (with no service packs, or with SP1, or with SP2) and servers, NT 4 workstations and servers with all kind of service packs, dual boot NT/98 machines, 95, 95 OSR2, 98, 98 SE workstations (did I forgot something?). We are all running happily programs like DOS/4GW Heretic shareware (I don't want to know how is able to run on a W2K machine :) - and I finished the first episode :)) I believe that over 90% of these 'restart' (??) problems are caused by wrong installation or configuration, misunderstandings or bad using... A visit - from time to time - on http://www.ntfaq.com/ - shows (for me, at least) how stupid I was (hope I'm not still stupid...), how I did not used help, read documentations and articles etc. Example? RedCode removal. After two days or installing Exchange, running isinteg and eseutil, a simple visit to MS website offered me the 5 minutes solution to get rid of RedCode 2. 'What's worst than a stupid person? A stupid person that is also an administrator' PS Speaking of 'restarting engineers': there are also 'restarting programmers'. A friend of mine told me how a programmer avoided to call delete for previously allocated memory. Of course, a simple run of BoundsChecker showed a zillion of memory leaks. Asked 'why you don't free the memory?', the man replied: 'because the program crashes'. In this way, the restart seems, indeed, the one and only solution. And that is valid also for people like him that creates a font and don't "DeleteObject" it, calls NetApi_XXX and forget to NetApiBufferFree, or pMalloc->Release(), or whatever you have in mind. X|

              N J D 3 Replies Last reply
              0
              • S Sardaukar

                ...since our servers, for example, are alive and running (with an exception, thanks to electric power company :( ) from 5? 6 months? True, there were seevral restarts (but that's because some patches and upgrades were applied and Windows requires restart. This is, indeed, unpleasant, but is something else). And these servers hosts SQL Servers, IIS, Exchange, Terminal Server, schedulers, printers - that means everything you need for a Windows NT/2000 server to get into trouble :)... And that's not all. Also some guys from our company - not me, of course :) - are testing NT services, network managers, IP tracers, remote system editing tools, user and printers manager, desktop switchers, an economical software - which is not big, but it has several thousands windows inside :) - , all of us perform huge print jobs etc. etc. etc. (Let's not forget the Starcraft combats during work time). Also, we have here Windows 2000 workstations (with no service packs, or with SP1, or with SP2) and servers, NT 4 workstations and servers with all kind of service packs, dual boot NT/98 machines, 95, 95 OSR2, 98, 98 SE workstations (did I forgot something?). We are all running happily programs like DOS/4GW Heretic shareware (I don't want to know how is able to run on a W2K machine :) - and I finished the first episode :)) I believe that over 90% of these 'restart' (??) problems are caused by wrong installation or configuration, misunderstandings or bad using... A visit - from time to time - on http://www.ntfaq.com/ - shows (for me, at least) how stupid I was (hope I'm not still stupid...), how I did not used help, read documentations and articles etc. Example? RedCode removal. After two days or installing Exchange, running isinteg and eseutil, a simple visit to MS website offered me the 5 minutes solution to get rid of RedCode 2. 'What's worst than a stupid person? A stupid person that is also an administrator' PS Speaking of 'restarting engineers': there are also 'restarting programmers'. A friend of mine told me how a programmer avoided to call delete for previously allocated memory. Of course, a simple run of BoundsChecker showed a zillion of memory leaks. Asked 'why you don't free the memory?', the man replied: 'because the program crashes'. In this way, the restart seems, indeed, the one and only solution. And that is valid also for people like him that creates a font and don't "DeleteObject" it, calls NetApi_XXX and forget to NetApiBufferFree, or pMalloc->Release(), or whatever you have in mind. X|

                N Offline
                N Offline
                NormDroid
                wrote on last edited by
                #7

                We haven't restarted our Windows 2000 Advance Server since March 2001. We stop/start to add new hardware. Also you'll find the more 'unstable' software you load onto to your server the more liely it is to: a. Crash b. Run out of memory So it seems it's the software running on the server and not the server it's self that is the problem. :|

                J 1 Reply Last reply
                0
                • G George

                  I will only focus on the rebooting - it is true that companies are regularly rebooting the windows based servers to ensure proper operation. I think it is once a week or so - and it seems to be the recommended by M$ procedure actually.

                  A Offline
                  A Offline
                  Anders Molin
                  wrote on last edited by
                  #8

                  Yea right... NOT. I have had several NT/2000 based servers with uptimes >= 200 days. - Anders Money talks, but all mine ever says is "Goodbye!"

                  G R 2 Replies Last reply
                  0
                  • N NormDroid

                    We haven't restarted our Windows 2000 Advance Server since March 2001. We stop/start to add new hardware. Also you'll find the more 'unstable' software you load onto to your server the more liely it is to: a. Crash b. Run out of memory So it seems it's the software running on the server and not the server it's self that is the problem. :|

                    J Offline
                    J Offline
                    jkgh
                    wrote on last edited by
                    #9

                    I'm instantly reminded of the award Trigger (of Only Fools and Horses) got for cost cutting. When questioned by Del and Rodders he said sure it's the same broom, but its had 14 new heads and 25 new handles. :-D :rose: C++/C# Student. Wither Thee VB.Net.

                    1 Reply Last reply
                    0
                    • A Anders Molin

                      Yea right... NOT. I have had several NT/2000 based servers with uptimes >= 200 days. - Anders Money talks, but all mine ever says is "Goodbye!"

                      G Offline
                      G Offline
                      George
                      wrote on last edited by
                      #10

                      200 days - how do you aplly the security patches and other then? I believe it will often require reboot...

                      A 1 Reply Last reply
                      0
                      • D David Wulff

                        Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


                        Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

                        T Offline
                        T Offline
                        Tim Smith
                        wrote on last edited by
                        #11

                        When a Linux user screws up Windows, it is because Windows is a sucky operating system. When a Linux user screws up Linux, it is because he made a mistake. I did some consulting for GA Tech and it was really funny. They were trying to write their Windows application as if it was a Unix system. Wow, what a shock, tons of problems. I came in there and rewrote the Unix crap to Windows and WOW, what a shock, things started working just fine. As far as Windows not being able to do mission critical operations, WRONG!!! Windows is use in a HUGE number of mission critical applications. It took over industrial automation. Tim Smith Descartes Systems Sciences, Inc.

                        J 1 Reply Last reply
                        0
                        • D David Wulff

                          Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


                          Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

                          A Offline
                          A Offline
                          Anders Molin
                          wrote on last edited by
                          #12

                          David, I always *love* your opinions :) - Anders Money talks, but all mine ever says is "Goodbye!"

                          D 1 Reply Last reply
                          0
                          • G George

                            200 days - how do you aplly the security patches and other then? I believe it will often require reboot...

                            A Offline
                            A Offline
                            Anders Molin
                            wrote on last edited by
                            #13

                            You are right about that. But those servers was only used internally behind a firewall, and I don't always apply all hotfixes on internally servers. - Anders Money talks, but all mine ever says is "Goodbye!"

                            1 Reply Last reply
                            0
                            • A Anders Molin

                              Yea right... NOT. I have had several NT/2000 based servers with uptimes >= 200 days. - Anders Money talks, but all mine ever says is "Goodbye!"

                              R Offline
                              R Offline
                              realJSOP
                              wrote on last edited by
                              #14

                              They must be on vanilla systems with no updated drivers and no human input, with no connection to the outside world. :)

                              A 1 Reply Last reply
                              0
                              • M Michael Dunn

                                Linux zealots never let the facts get in the way of a good religious war. ;) --Mike-- http://home.inreach.com/mdunn/ You are the weakest link, GOODBYE!

                                R Offline
                                R Offline
                                realJSOP
                                wrote on last edited by
                                #15

                                That's wholly unfair. The Windows zealots are just as bad.

                                T 1 Reply Last reply
                                0
                                • S Sardaukar

                                  ...since our servers, for example, are alive and running (with an exception, thanks to electric power company :( ) from 5? 6 months? True, there were seevral restarts (but that's because some patches and upgrades were applied and Windows requires restart. This is, indeed, unpleasant, but is something else). And these servers hosts SQL Servers, IIS, Exchange, Terminal Server, schedulers, printers - that means everything you need for a Windows NT/2000 server to get into trouble :)... And that's not all. Also some guys from our company - not me, of course :) - are testing NT services, network managers, IP tracers, remote system editing tools, user and printers manager, desktop switchers, an economical software - which is not big, but it has several thousands windows inside :) - , all of us perform huge print jobs etc. etc. etc. (Let's not forget the Starcraft combats during work time). Also, we have here Windows 2000 workstations (with no service packs, or with SP1, or with SP2) and servers, NT 4 workstations and servers with all kind of service packs, dual boot NT/98 machines, 95, 95 OSR2, 98, 98 SE workstations (did I forgot something?). We are all running happily programs like DOS/4GW Heretic shareware (I don't want to know how is able to run on a W2K machine :) - and I finished the first episode :)) I believe that over 90% of these 'restart' (??) problems are caused by wrong installation or configuration, misunderstandings or bad using... A visit - from time to time - on http://www.ntfaq.com/ - shows (for me, at least) how stupid I was (hope I'm not still stupid...), how I did not used help, read documentations and articles etc. Example? RedCode removal. After two days or installing Exchange, running isinteg and eseutil, a simple visit to MS website offered me the 5 minutes solution to get rid of RedCode 2. 'What's worst than a stupid person? A stupid person that is also an administrator' PS Speaking of 'restarting engineers': there are also 'restarting programmers'. A friend of mine told me how a programmer avoided to call delete for previously allocated memory. Of course, a simple run of BoundsChecker showed a zillion of memory leaks. Asked 'why you don't free the memory?', the man replied: 'because the program crashes'. In this way, the restart seems, indeed, the one and only solution. And that is valid also for people like him that creates a font and don't "DeleteObject" it, calls NetApi_XXX and forget to NetApiBufferFree, or pMalloc->Release(), or whatever you have in mind. X|

                                  J Offline
                                  J Offline
                                  Jarek G
                                  wrote on last edited by
                                  #16

                                  One big problem today is that people mix C with C++ its okey some times, but when you writing apps in Windows you aint always get a great result when mixing C with C++! One shall use "new" insted of "malloc" etc etc. Then we have a new set of lib's in the std neamespace so old "new" is not reacting as the new one! More "try" and "catch" less "I think its working?" IMHO Jarek

                                  S 1 Reply Last reply
                                  0
                                  • R realJSOP

                                    They must be on vanilla systems with no updated drivers and no human input, with no connection to the outside world. :)

                                    A Offline
                                    A Offline
                                    Anders Molin
                                    wrote on last edited by
                                    #17

                                    No connection to the outside world, yes. It is internally used servers. A webserver will never get this kind of uptime because of all the hotfixes it need every once in a while... No human input, err..., they are servers. How often do you use the keyboard on a server? No updated drivers, well, if I have an Exchange Server or a SQL Server, why do I want to update drivers when the server runs perfectly fine? But my point is, the Windows Servers runs perfectly fine without being rebooted all the time! - Anders Money talks, but all mine ever says is "Goodbye!"

                                    1 Reply Last reply
                                    0
                                    • J Jarek G

                                      One big problem today is that people mix C with C++ its okey some times, but when you writing apps in Windows you aint always get a great result when mixing C with C++! One shall use "new" insted of "malloc" etc etc. Then we have a new set of lib's in the std neamespace so old "new" is not reacting as the new one! More "try" and "catch" less "I think its working?" IMHO Jarek

                                      S Offline
                                      S Offline
                                      Sardaukar
                                      wrote on last edited by
                                      #18

                                      It was only about new/delete. But, anyway, this is not the main idea. The fact was the programmer (?) was too lazy to debug the code. For sure he/seh tried to delete more than allocated, or to delete a 0xcdcdcdcd pointer, or something like this. If you want to avoid these malloc/delete, new/free, Local, Global etc., you have always the alternative of COM allocator CoGetMalloc...

                                      1 Reply Last reply
                                      0
                                      • D David Wulff

                                        Feel like a nice long read this fine Sunday morning? Try staying awake long enough to read through this discussion thread (note, it is long, very very long). It has been going on since February, but it serves as a good example of Microsoft’s bad choice of not going to press to counter these things when the rumours first emerged. The damage was already done six months ago, and I doubt many of those 14 year olds will back down now. In summary: A large majority of the contributors to the debate seem to have accepted the following as fact, and were openly preaching them: * Windows XP requires registration * Windows XP is .NET * Windows XP can only be rented (this view was shared by many people. Too many) * Windows XP only has the cartoony interface * Office XP can only be rented * Upgrades to new versions should be free (ha – tell that one to my local car dealer) * .NET is the new version of Windows * Windows XP is for home users only, “who do not have the technical expertise to maintain a full-fledged operating system”. * Microsoft always makes crappy, incompatible hardware drivers, which are the main reason Windows is so unstable. * Site licenses of Windows and Office XP will require activation – no, sorry, registration. I don’t think anyone drew the line between activation and registration until the last few pages. * Microsoft are trying to prevent you from installing Windows XP on all your home PC’s. They want you to buy a new copy for each machine. Heaven forbid such a thing. * You need to be connected to the Internet to use Word XP. As in connected to type anything. * You will require an Internet connection to use a web service. And next thing you know, you’ll need a connection to surf the net! * Registration will cost $$$. I guess they meant activation. One guy even talked about starting a "ribbon" style campaign to educate people about Windows XP. I sure hope he didn’t succeed. And now for the best bits:


                                        Issues in Windows 98SE/2k: 1. 98: Windows won't shut down. It hangs. 2. 98: The Start button doesn't say "Start." It is a random mix of colors that change every time it's clicked. 3. 98 and 2k: Icons randomly disguise themselves as other icons. 4. 2k: Explorer crashes during idle time. The desktop color is displayed for a few seconds before the applications reappear. 5. 2k: The desktop refuses to repaint itself. 6. 2k: The cursor is repl

                                        C Offline
                                        C Offline
                                        Chris Losinger
                                        wrote on last edited by
                                        #19

                                        after 12 hours of trying to install fscking WinNT on a blank system, i have to say: MS software is crap. right now, i'm going on my tenth total new install and each time, just when i think i'm going to be able to finish, some driver or app wil fsck up the OS so bad that i can't even launch programs - all i get is a message about some missing symbol in kernel32. yeah, great stuff. :( -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com

                                        A T D 3 Replies Last reply
                                        0
                                        • C Chris Losinger

                                          after 12 hours of trying to install fscking WinNT on a blank system, i have to say: MS software is crap. right now, i'm going on my tenth total new install and each time, just when i think i'm going to be able to finish, some driver or app wil fsck up the OS so bad that i can't even launch programs - all i get is a message about some missing symbol in kernel32. yeah, great stuff. :( -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com

                                          A Offline
                                          A Offline
                                          Anders Molin
                                          wrote on last edited by
                                          #20

                                          What is the errormessage? Maybe it's just a single driver that corrupts the entire system... Anyway, NT 4.0 is from 1996, it's a looong time in this business, try with a Linux from 1996, do you thing it's more easy? To make a perfectly running NT 4.0 takes some "touch" with the system, Win2k is a lot more easy... (no offence, really) - Anders Money talks, but all mine ever says is "Goodbye!"

                                          C 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups