cluberti

Could you post the log file?

The only way to have an @msn.com address is to be an MSN subscriber. Otherwise, he'll have to create another email address and use that, and no, email addresses generally aren't portable like phone numbers are. If he terminates his contract with MSN, he'll lose his @msn address.

You could always grab a network trace with Wireshark of this occurring, and see if you're getting any responses back from cnn.com, or if you get any abberant responses from your DNS servers when you request cnn.com.

"Centro" is in the same vein as the "Small Business Server" product line - think of it as Windows Server "Medium Business Servers" (it takes 3 servers to run). It installs (currently, anyway) Windows Server Longhorn, Exchange Server 2007, System Center Essentials, SQL Server 2005, Forefront security, and ISA Server, and has a custom MMC that allows management of all of these systems from one location.

The only reasons for taskbar icons to exit when still running would be that the explorer.exe process terminated and restarted itself - have you installed anything recently that would've had shell hooks for your DVD drive, or media files? If you run autoruns and shellexview to disable all non-Microsoft startup items, services, and shell extensions, and reboot, does the problem continue?

The .net framework is a wholly contained runtime environment, found in the \Windows\.NET Framework\<version>\ folder once installed. If you've got an application that is complaining about Msvcr80.dll, which is part of the Microsoft Visual C runtime library 8.0 (hence the beginning of the file name "msvcr"), the application vendor should have provided the redistributable with their installer package. You may have to reinstall the application to make it work, or, you may be able to simply copy the file to the \Windows\system32 folder and get lucky (if it's not already there). I do second the vote against using Norton-branded products as well, but that's not of much help to you at the moment .

Well, have you tried connecting to a different port on your router (hoefully it's got more than one port for internal users)? If you've got a different cable, that would indicate that theire's either something wrong with the NIC or the router port, assuming the new cable is good. One thing you can do is switch the ends of the cable, so that the end that was connected to the computer is now plugged into the router (and vice versa).

It could very well be zone alarm - one thing you can try is to boot into safe mode w/ networking, and see if you get the same behavior there. If so, it's likely your hosts file, and if not, it's likely a 3rd party product (like zonealarm).

This is well described on Microsoft's main site and technet, regarding the Windows 2000 security model: http://www.microsoft.com/technet/prodtechn...c/07w2kada.mspx http://technet2.microsoft.com/WindowsServe...3.mspx?mfr=true

Does it never go to your homepage, or once IE7 is open can you refresh or browse to it afterwards?

Just checking in - any luck in getting a dump, or tracking this down, war4peace?

Did you configure the Win98 client to use the W2K3's IP address as the DNS server?

I agree - now that you have a SIF file you can reference, read very thoroughly the unattended guide here, and visit and post questions in the unattended sections of this forum for anything else you need clarity on. Good luck!

The issue is that power states, until dual-core (and multi-core) processors, used to be able to be handled and addressed per processor. Now, with more than one core on a processor die, the power state and performance state functionality of a processor can actually be two physical cores on one proessor, and the kernel needs to understand that one physical processor may expose 2 *real* processors and those are not virtual processor cores. Again, with hyperthreading, this wasn't a problem, as the exposed processors were virtual and both were actually just one processor. With actual cores, this becomes a power and state switching problem that was addressed in the hotfix kernel, to a point. However, Vista and Longhorn's kernels "understand" multi-core processors, whereas XP and 2003's kernels only "sort-of" understand it, and have been modified to work around their shortcomings. They'll use both processors for running code properly, yes, but other power-specific and performance-specific features internal to the processors may not be supported 100%.

[Data] AutomaticUpdates = NO AutoPartition = 1 MsDosInitiated = 0 UnattendedInstall = YES [Unattended] Unattendmode = FullUnattended UnattendSwitch = YES OemPreinstall = YES OemPnPDriversPath = drivers\audio;drivers\chipset;drivers\misc\wireless;drivers\modem;drivers\network;drivers\RAID;drivers\touchpad;drivers\video OemSkipEULA = YES TargetPath = WINDOWS Filesystem = ConvertNTFS DUDisable = YES Hibernation = NO WaitForReboot = NO DriverSigningPolicy=Ignore Repartition = YES AutoActivate = NO [GuiUnattended] TimeZone = 035 AdminPassword = * EncryptedAdminPassword = NO OemSkipWelcome = 1 OEMSkipRegional = 1 AutoLogon = YES AutoLogonCount = 1 [SetupParams] UserExecute=%systemdrive%\temp\unattend.cmd [GuiRunOnce] "%systemdrive%\temp\xplode.exe /xml:%systemdrive%\temp\applications.xml /log:%systemdrive%\temp\applications-install.log" [UserData] FullName = USER OrgName = ORG ComputerName = * ProductKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX [Display] BitsPerPel = 32 Xresolution = 1024 YResolution = 768 [Identification] JoinWorkgroup = WORKGROUP [Networking] InstallDefaultComponents = Yes [NetOptionalComponents] Beacon = 0 [Components] Accessopt = Off CertSrv = Off CertSrv_Client = Off CertSrv_Server = Off Chat = Off Deskpaper = Off Dialer = Off Fax = Off Fp_extensions = Off FP_Vdir_Deploy = Off Freecell = Off Hearts = Off IIS_Common = Off IIS_Doc = Off IIS_FTP = Off IIS_HTMLa = Off IIS_Inetmgr = Off IIS_NNTP = Off IIS_NNTP_Docs = Off IIS_Pwmgr = Off IIS_SMTP = Off IIS_SMTP_Docs = Off IIS_WWW = Off IIS_WWW_Vdir_Printers = Off IIS_WWW_Vdir_TerminalServices = Off IISDbg = Off Indexsrv_system = Off LicenseServer = Off Media_utopia = Off Minesweeper = Off Mousepoint = Off Msmsgs = Off MSMQ_ADIntegrated = Off MSMQ_Core = Off MSMQ_HTTPSupport = Off MSMQ_LocalStorage = Off MSMQ_MQDSService = Off MSMQ_RoutingSupport = Off MSMQ_TriggersService = Off Msnexplr = Off Netoc = Off OEAccess = Off Pinball = Off Solitaire = Off Spider = Off WMAccess = Off zonegames = Off [PCHealth] ER_Display_UI = 0 ER_Enable_Applications = None ER_Enable_Kernel_Error = 0 ER_Enable_Reporting = 0 ER_Enable_Windows_Components = 0 ER_Force_Queue_Mode = 0 ER_Include_MSApps = 0 ER_Include_Shutdown_Errs = 0 [Shell] DefaultStartPanelOff = NO DefaultThemesOff = NO [SystemFileProtection] SFCQuota = 0 [SystemRestore] MaximumDataStorePercentOfDisk = 5 RestorePointLife = 7 [Branding] BrandIEUsingUnattended = Yes [URL] Home_Page = http://www.google.com Search_Page = http://www.google.com/ie_rsearch.html AutoConfig = 0

No, not really. The problem with XP's setup is that it's a holdover from the NT days, and has limitations that are frustrating. That's one of the reasons the installer for Vista was changed completely. There are programs out there to help with making it better (like nLite or SetupStudio), but nothing will replace it.

No, it's saying it was tested, and does not work on Vista. Projects that rely on mscomm32.ocx (or anything else under the "Tested and not working" section) will fail to work properly on Vista. Only the top block of components were shipped with Vista, and those are the only VB6 functional components on Vista. You can include the others if you'd like, but they won't work.

OK, after looking at the data you uploaded yesterday, it looks like something called "badgesmenu.dll" is doing an unregisterserver event for a driver, and causing the application to crash. I don't know what this app does, or even what it's doing after the DllUnregisterServer event, but it's definitely something the system does NOT like . Also, since this does appear to modify system icon resources, and I'm guessing on the fly, it could very well be misbehaving. Here's the data - if the timestamp on that .dll is really correct, I'm not surprised it's not working without crashing: ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 0933dfa4 063398b1 0933e02c 06339b29 0933e014 badgesmenu+0x1769 0933e014 0633a3ed 0633a760 00000000 7fffffff badgesmenu!DllUnregisterServer+0xeec9 0933e094 7ca0fafd 090844e0 004b04a6 00000000 badgesmenu!DllUnregisterServer+0xfa05 0933e230 7ca103b2 02b14118 02be6af0 00000005 shell32!HDXA_AppendMenuItems2+0x2d0 0933e2b4 7caa7e26 00000000 004b04a6 02182860 shell32!CDefFolderMenu::QueryContextMenu+0x2e8 0933e5cc 7caaadde 02a50120 00000010 0000011c shell32!CDefView::_DoContextMenuPopup+0xfb 0933e618 7c9fa58c 01a2011c 00000000 02adc008 shell32!CDefView::ContextMenu+0x1e4 0933e78c 7c9f1da1 003b0414 0000007b 004e0844 shell32!CDefView::WndProc+0x840 0933e7d0 77d48734 003b0414 0000007b 004e0844 shell32!CDefView::s_WndProc+0x72 0933e7fc 77d48816 7c9f1d4b 003b0414 0000007b user32!InternalCallWinProc+0x28 0933e864 77d4b4c0 000a5b48 7c9f1d4b 003b0414 user32!UserCallWinProcCheckWow+0x150 0933e8b8 77d4b50c 00650eb0 0000007b 004e0844 user32!DispatchClientMessage+0xa3 0933e8e0 7c90eae3 0933e8f0 00000018 00650eb0 user32!__fnDWORD+0x24 0933e904 77d494be 77d4b42d 004e0844 0000007b ntdll!KiUserCallbackDispatcher+0x13 0933e958 77d4b3f9 004e0844 0000007b 00430868 user32!NtUserMessageCall+0xc 0933e974 5ad71af6 004e0844 0000007b 00430868 user32!RealDefWindowProcW+0x47 0933e9cc 5ad71b3d 00000000 00000000 00430868 uxtheme!_ThemeDefWindowProc+0x16e 0933e9e8 77d4bb15 004e0844 0000007b 00430868 uxtheme!ThemeDefWindowProcW+0x18 0933ea30 7cb218b9 004e0844 0000007b 00430868 user32!DefWindowProcW+0x6b 0933ea68 77d48734 004e0844 0000007b 00430868 shell32!CDUIView::_DUIHostWndProc+0xf7 start end module name 06310000 06352000 badgesmenu C (export symbols) badgesmenu.dll Loaded symbol image file: badgesmenu.dll Image path: d:\Program Files\Badges 1.0.1.0\badgesmenu.dll Image name: badgesmenu.dll Timestamp: Fri Jun 19 18:22:17 1992 (2A425E19) CheckSum: 00000000 ImageSize: 00042000 File version: 1.0.0.0 Product version: 1.0.0.0 File flags: 0 (Mask 3F) File OS: 4 Unknown Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0419.04e3 CompanyName: Shedko D. aka LeVeL ProductName: Badges : Context menu InternalName: badgesmenu.dll OriginalFilename: badgesmenu.dll ProductVersion: 1.0 FileVersion: 1.0.0.0 FileDescription: Badges : Context menu LegalCopyright: (c) Shedko D. aka LeVeL, 2006 LegalTrademarks: none

You can't make an unsolicited remote desktop request to an XP Home machine, which gets most people.

STOP 0x1a is usually one of three things - winlogon.exe, lsass.exe, or csrss.exe. Since it did write a dump file, I'd bet it's winlogon.exe crashing - usually, when lsass.exe or csrss.exe crash, you lose your security subsystem or you lose the context switching subsystem, and as a result you can't really write anything to disk. This isn't 100% accurate all of the time (I've seen dumps from lsass.exe and csrss.exe STOP 0x1a's before, but they're rare), but if I had to guess I'd say winlogon.exe crashed. If it's a 3rd party driver, the dump should tell us who caused the pool corruption... Did you perhaps install any new software or hardware drivers, any new VPN or remote control software, or any networking software recently? Also,make sure your machine is clean... Edit: Actually, after looking at the minidump, it looks like the function MiRemovePageByColor from the module bdss.exe is causing the dumps, which usually signifies an .exe or hardware problem - bdss.exe belongs to BitDefender antivirus - can you uninstall that temporarily to see if the problem goes away?

Actually, if your VB6 project uses mscomm32.ocx, it won't work on Vista (it's in the tested and not working portion of the runtimes as per the URL below): http://msdn2.microsoft.com/en-us/vbasic/ms788708.aspx

No, because x64 doesn't allow boot diskettes anymore. It isn't going to work - you either use the recovery console or WinPE to fix your x64 install, and YOU HAVE TO INSTALL FROM CD on the initial x64 installl - booting with floppies is no longer supported in x64 Windows editions.

And I'm assuming you haven't disabled processing of objects in the GPO's, correct? Have you checked SYSVOL on this DC to make sure it's the same as the other two?

You actually don't, really - if the software's repair function causes winlogon to re-initialize it's registry settings, winlogon does have a function, I believe, that checks to make sure that the msgina.dll will load first (as a default install would have). Software that replaces or loads a custom gina.dll will require you to "fix" the registry to make it work after a repair if the repair touches winlogon at all, and there's no way around it. By the way, software that uses a custom gina will no longer work on Vista, just an FYI.

Almost everyone here needs to read this post and the forum rules. Let's try to keep everything civil here, there's no reason to get upset. We now know what the original poster wants to accomplish, and anyone that can help please do.