ryang

I've been asked to investigate whether it is possible to disable or remove the ability to close a program, more specifically, by clicking on the "X" in the top right. Reason: The program in question is quite capable of closing itself, once the user has logged out that is.. However, after much education the users still don't seem to get it. I thought I'd seen something that could do this, but it might've been a Linux thing. I know IceWM can control the windows completely, from location, to buttons, etc. I found a program (WinTopMost or something like that..), but it's shareware, rather expensive and it has to be run WITH the application.. If it was a wrapper that launched the app. I'd be fine, but it has to run before the app. is launched, painful. If anyone has got any ideas I'd really appreciate your input.

Well I'll be damned... That worked like a charm!! Thanks heaps for that.

Oi, you're joking right?? Surely there's another way around this... I've now got 3 updates "waiting" to be installed because of this error.

That'd be a negative on Office 2000 BTW... Only supports Office XP and 2003, and whatever they bring out in future obviously.

I would've agreed with you, until earlier this week that is. I had to try and run a tool called 'netxfer' that is design to recover failed firmware on some of our older thin-clients.. For some crazy reason, this tool NEEDED the MS JVM installed. Thankfully I had a copy of WinXP SP1 floating around, so I just grabbed it from there.

Microsoft Update is definately a separate install to WU6... Anyone found a "nice" way of installing it yet? I nice executable from MS would be appreciated, but I haven't had any luck finding one...

KB890830 is now available for Windows 2000, under WU6.. Wasn't available under WU4 (default for W2k) as of yesterday.

Just to give you a hand, here's the list of updates I had to install on a bare SP4-UR1 system; 897715 - Vulnerability in Outlook Express could allow remote code execution 883939 - Cumulative security update for Internet Explorer 896422 - Vulnerability in Server Message Block could allow remote code execution 890046 - Vulnerability in Microsoft agent could allow spoofing 896358 - A vulnerability in HTML Help could allow remote code execution 894320 - Vulnerability in Web View could allow remote code execution 873374 - Microsoft GDI+ Detection Tool 842773 - Update package that includes BITS 2.0 and WinHTTP 5.1 832483 - Buffer overrun in an MDAC function could allow code execution 814078 - Flaw in Windows Script Engine may allow code to run 893803 - Windows Installer 3.1 (v2) Partial credit goes to Incroyable HULK and his fantabulous page (http://www.msfn.org/board/index.php?showtopic=31886).

QEmu really isn't usable unless you are running linux and can use the accelleration offered by the kernel enhancements... Personally I use VMWare, but I haven't tried VirtualPC.

http://www.microsoft.com/windowsserver2003/sbs/default.mspx It's not a beta AFAIK. SBS has always been a bit of a mish-mash of products though, so it's not really a suprise that it wasn't recognised. If you are ONLY using XPCREATE to integrate drivers, then you might also want to check out nLite. I have a feeling it won't support it, but it doesn't hurt to try.

I recently created a Win2k CD with XPCREATE and have had no problems at all.. Except for the small DirectX issue that is currently being researched, but that's normal. I would say however that it is directly related to you having problems with the IE components. Hopefully someone else on here can help you in that regard.