Jump to content
Compatible Support Forums

Toby

Members
 View Profile  See their activity

  • Content count

    314

  • Joined

  • Last visited

Posts posted by Toby

  6. Posted

    Then your boot.ini should look like this:

     

    [boot loader]

    timeout=30

    default=multi(0)disk(0)rdisk(0)partition(2)\WINNT

    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

     

     

    You also need the following files in the root of your c:

     

    ntldr

    ntdetect.com

     

    Good luck.

     

    /Toby

     

    edit: wrong spelling of filename..

  11. Posted

    NOTE: Level 2 (L2) CPU cache size can be sized this way, ONLY IF using earlier CPUs: Intel (and compatibles) 386, 486, Pentium, Pentium Pro, AMD K5/K6/K7, Cyrix, etc, with off-chip L2 cache SRAM memory (external, off the CPU die).

     

    If using newer CPUs: Intel Pentium II/III/IV/Celeron/Xeon, AMD Athlon/Duron/Thunderbird, etc, with on-chip L2 cache SRAM memory (internal, on the CPU die), L2 cache size can *NOT* be altered!

     

     

    /Toby

  14. Posted

    Yes, this patch is critical. I can not remember MS ever wrote this in the recommendation:

     

    "Who should read this bulletin: All web server administrators using Microsoft® Windows® 2000

     

    Impact of vulnerability: Run code of attacker’s choice in system context.

     

    Recommendation: Microsoft strongly urges all IIS 5.0 server administrators to install the patch immediately."

     

     

    Patch and more info:

    http://www.microsoft.com/technet/security/bulletin/MS01-023.asp

     

    /Toby

  15. Posted

    Delete this key in the registry and reboot:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]

     

    This key makes win2k look for scheduled tasks and is causing the delay when browsing win9x-machines.

     

    /Toby

  17. Posted

    Clutch, I have no experience of Exchange. I use this for my workstation at home for my pop-mail, but it works when I connect to work over VPN to check my Excange-mail as well. (If I take a guess everthing is allowed at work execpt .vbs).

     

    What this app does is that it edits the registry and adds the values for you. (They always says I'm lazy, wonder why ;))

     

    HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security

     

    It creates i stringvalue there called "Level1Remove" and with the data "exe;bat;com" or whatever you want to be able to save.

     

    The app gives you this in Outlook.

     

    I can't remember where I got it, but download it here if you want it.

     

    /Toby

  18. Posted

    I got really upset when I first found out about it. The main reason for this is that we have had some serious problems a while ago. The DomainControllers with SP6a would not drop the connections after users had logged in resulting in that after some time they would not respond at all and no one could log on. Some departments could work(logged in with cached info), but for others which have "flexible" offices they could not log on at all. The solution? Hotfix Pre SP7.

     

    This Hotfix was not easy to find and MS support (in Sweden) was totally clueless about the problem. If they had released SP7 this fix would be included (and many more), lets just hope that MS put up a real *good* site with detailed info on the hotfixes then it might be ok.

     

    However, if I need to install a new server in say 6months, I first have to install NT, SP6a and then spend alot of time looking for hotfixes that might be required for this server. I don't like it. If the SP would keep coming on a regullar basis I would'nt have to check the hotfixes, just install the latest SP and be set. A waste of time this is, searching/applying Hotfixes.

     

    And to say like MS that this is what the customers wants I take as a lie.

     

    RussellWild, are you that clueless ?!

    Even though most of our servers running Win2k now, there's many servers running applications that only will work on NT4. All is not about DirectX and games you know....

     

    /Toby

  19. Posted

    If I where you I would reinstall Office. It only takes a couple of minutes instead of trying to repair wich can take a long time. And as you sayd, zip-files should not be blocked in the first place. But don't throw away the file I sent, it will be useful for unblocking .exe .com .bat and more once you got it working again.

     

    Sorry it did not work, but I thoght it was worth a try...

     

    (Clutch, I did send him a zip-file too, after spotting he got yahoo-mail I thought he could save it through the browser.)

     

    /Toby

  21. Posted

    This is from the the newsletter I just recived form win2knews.com. If this information is correct it really SUCKS!!.

     

    Have any of you heard anything in this matter?

     

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

    No NT 4 Service Pack 7 At All!

     

     

    You may be aware of the NTSYSADMIN list that Sunbelt sponsors. It's a great (free) forum to discuss system administration issues for both NT and W2K. We have well over 4,000 pros on there discussing very interesting threads that hash out problems and solutions. Since we have increased our double T-1 to a T3 (now driven via optics), and downgraded the Lyris listserver software back to an earlier version, performance has soared. Imagine the news I got via the NTSYSADMIN list: WinNT4 Service Pack 7 will never arrive!

     

    This despite my last issue where I expected it to arrive end Q3. I was contacted by some one 'in the know' that this was incorrect. Here is the copy that one of the list subscribers just received from their Microsoft Technical Account Manager. I'm quoting verbatim here, so there will be no confusion caused by me interpreting anything. here goes:

     

    "Windows NT 4.0 Service Pack 6a, the most recent service pack for Windows NT, was released in November of 1999. Since then, Microsoft has been supporting our customers with a series of hotfixes in response to specific concerns, including security vulnerabilities.

     

    "Microsoft intends to continue supporting customers by making hotfixes available as they are needed. However, since the release of Service Pack 6a, the frequency of critical problems reported to Microsoft has declined significantly. Microsoft originally planned on releasing Service Pack 7 late last year, approximately 1 year after the release of SP6a.

     

    "At the time, Microsoft had produced relatively few post-SP6a hotfixes, and decided to delay SP7 until Q3 of 2001. The frequency of hotfixes has continued to decline, and now, well over 1 year beyond the last SP, we still have made fewer fixes than were included with either SP5 or SP6.

     

    "We discussed with a number of our customers their use of recent service packs, and their requirements for an additional service pack. From these discussions we learned that most customers are running a combination of Service Pack 5 and Service Pack 6; in some cases with 3-5 additional hotfixes. These customers told us that these service packs, particularly Service Pack 6a, have been very stable.

     

    "There were three reasons we heard that customers were anticipating Service Pack 7: An easy mechanism for deploying the security fixes Microsoft has publicly released since SP6a. Availability of the Windows NT 4.0 Active Directory client, originally planned to be part of SP7 - now available for download at

    http://www.microsoft.com/windows2000/news/bulletins/adextension.asp

    High Encryption for International versions of Windows NT which is now available through Internet Explorer and downloadable at:

    http://www.microsoft.com/windows/ie/

     

    "Based on discussions with our customers, we have come to the conclusion that Service Pack 7 is not needed, but that an easy way to deploy our publicly released security fixes would be appreciated by many of our customers. It is clear to us that our customers would rather have a smaller, lightweight, easily deployable way to secure their systems, rather than potentially disrupt their stable environments with another large service pack. Microsoft is therefore planning to release a comprehensive rollup of all Windows NT 4.0 security vulnerabilities as a single package in Q3 2001.

     

    "Microsoft recognizes that some companies have been planning on a new service pack, especially since Microsoft had previously given indications that Service Pack 7 would be released. For customers who were planning on deploying Service Pack 7, we now encourage them to focus on completing rollouts of Service Pack 6a, in combination with the planned security pack. Microsoft will provide detailed instructions for deploying Service Pack 6a with the security pack.

     

    "While Microsoft will not offer any further service packs for NT 4.0, we are committed to providing regular service packs for the currently released operating system, Windows 2000. Service Pack 2 for Windows 2000 will be released in the near future. As new versions of Microsoft operating systems are released, Microsoft will continue to evaluate the need for service packs based on our customer's requirements and feedback, and the stability of the operating system." End Quote.

     

    Andrew Baker (one of the Guru's on the NTSYSADMIN list) commented 'tongue-firmly-in-cheek':

     

    Top 10 Reasons Why SP7 Was Cancelled:

     

    10.Win2K is selling better than expected so there's no reason to continue working on NT4.

    9. Giving each developer $1000 for every bug found was getting far too costly.

    8. Due to a softened economy, they've had to cut some costs, and NT4 bug fixes drew the short straw.

    7. The odd numbered Service Packs are the "good ones", so Win2K migrations would probably be put off for another 18 months.

    6. It was taking too long to get WPA integrated into SP7, so that work is being transported to Win2K SP2

    5. Trying to get the entire Service Pack to fit on one DVD was far too difficult.

    4. It just occurred to them that by Q3, they'd be supporting 5 OSes: Win98, WinME, WinNT, Win2K and WinXP, and they didn't want to get customer expectations too high.

    3. Marketing reminded Sr. Management that most folks would be consider 200MB service packs to be an OS install, not a patch.

    2. Win2K sales are slow, so several "Win2K Migration Incentives"have been established.

    1. It was becoming very difficult to entice anyone in the company to continue supporting NT4 when "everyone else" is getting to work with that cool .NET stuff

     

    You can subscribe to the NTSYSADMIN list here:

    http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

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

     

    /Toby

  25. Posted

    What a great game !!

     

    It's been a very long time since I had this kind of fun hardcore gaming. Thanks to all of you for the recommending smile

     

    Do you guys play online ?

    If so whats your nicks ? Mine's Toby, the same as on this Forum....

     

    See you online !

     

    /Toby

×