Won’t stop booting to PC DOS

I need a solution

I am working on and older PC with Ghost 2003. I know, but it’s an old computer. In the Ghost program in Windows, I selected what I wanted to image. The computer then rebooted into PC DOS but never fully launched Ghost. Now the computer will NOT boot back to Windows. 2 questions – How do I get it to boot back to Windows (and selcting “Skip Ghost DOS and boot into Windows doean’t work) and 2nd question, I have previously Ghosted boot drive I can use but I am scared it will try to boot to PC DOS as well. Is the “Boot to DOS” iset in the BIOS or something on the drive? Can I use the other boot disk without a problem?

Thank you all so much. This is a ral important computer and I need to get it running again as soon as I can.

0

Related:

Symantec detected “io.sys and msdos.sys” as WS.Reputation.1

I need a solution

Hi Team,

We have SEPM version 14. We have found symantec has detecting files  “io.sys and msdos.sys” as WS.Reputation.1 same has been qurantined and deleted by SEPM. but still we are see those file in system but size is 0 kb.

Also we have observed those files(io.sys and msdos.sys) are created by processntvdm.exe“. and this file belong to mircosoft and genuine process

Date size File
03/14/2018 07:34 AM GMT 0 IO.SYS
     
03/14/2018 07:34 AM GMT 0 MSDOS.SYS
     

Symantec Logs:

Filename Risk Original Location Computer Current Location Primary Action Secondary Action Action Description Date and Time
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Restart Required – Quarantine Restart Required – Delete Restart Required – The file was quarantined successfully. 12/4/2018 10:19
io.sys WS.Reputation.1 c: D00070-0061 Quarantine Restart Required – Quarantine Restart Required – Delete Restart Required – The file was quarantined successfully. 12/4/2018 10:18
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Quarantine Delete Performed Post-Reboot Risk Processing. 12/4/2018 9:54
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Quarantine Delete Performed Post-Reboot Risk Processing. 12/4/2018 9:54

Hash value of files io.sys and msdos.sys : E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 

Files path: C:/ io.sys and C:/ msdos.sys

Please confirme what basis symantec has detecting those files io.sys and msdos.sys as WS.Reputation.1. and let us know the reason?

0

Related:

The share name entered may not be accessible from some MS-DOS workstations. Are you sure you want to use this share name? %1: %0

Details
Product: Windows Operating System
Event ID: 4738
Source: System
Version: 5.0
Symbolic Name: APE2_SHARE_MSG_NONFAT
Message: The share name entered may not be accessible from some MS-DOS workstations. Are you sure you want to use this share name? %1: %0
   
Explanation

MS-DOS workstations can only recognize share names that fit the file naming requirements in MS-DOS. If you assign this name to the share, MS-DOS workstations will not be able to access it.

   
User Action

If you are sure this share will not need to be accessed from MS-DOS workstations, click Yes. Otherwise, click No.

Related:

IMPORT.EXE/EXPORT.EXE could not run because the file IMPORT.INI/EXPORT.INI could not be written. This may be because the NTVDM.EXE (MS-DOS) process used to run the previous IMPORT/EXPORT may not have terminated normally and is in a suspended state with the IMPORT.INI/EXPORT.INI file locked. Use the Windows 2000 Task Manager to see if the NTVDM.EXE process is still running but inactive (using 0% CPU time) and use the End Process command to terminate it.

Details
Product: Exchange
Event ID: 86
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_IMPEXP_INI_FILE
Message: IMPORT.EXE/EXPORT.EXE could not run because the file IMPORT.INI/EXPORT.INI could not be written. This may be because the NTVDM.EXE (MS-DOS) process used to run the previous IMPORT/EXPORT may not have terminated normally and is in a suspended state with the IMPORT.INI/EXPORT.INI file locked. Use the Windows 2000 Task Manager to see if the NTVDM.EXE process is still running but inactive (using 0% CPU time) and use the End Process command to terminate it.
   
User Action
Perform the user action specified in the message.

Related:

VU#535111: McAfee VirusScan Enterprise for Windows scriptproxy COM object memory corruption vulnerability

Vulnerability Note VU#535111

McAfee VirusScan Enterprise for Windows scriptproxy COM object memory corruption vulnerability

Original Release date: 13 Dec 2016 | Last revised: 19 Dec 2016

Overview

McAfee VirusScan Enterprise for Windows scriptproxy COM object contains a memory corruption vulnerability.

Description

According to the reporter, McAfee VirusScan Enterprise for Windows version 8.7i through at least 8.8 patch 7 contains a scriptproxy COM object that is vulnerable to the following:

CWE-824: Access of Uninitialized Pointer

According to the reporter, when attempting to load the McAfee VirusScan Enterprise scriptproxy COM object DLL via CLSID in an HTML document through Internet Explorer, the DLL may crash in such a way as to cause an access violation on the instruction pointer, which may lead to denial of service.

The CERT/CC has not received a CVE ID assignment from McAfee for this issue at this time. Intel Security, which owns McAfee, has provided the following response:

    Intel Security takes any claim of this kind very seriously. We have requested and are awaiting the information we require to conduct our assessment. We look forward to receiving this information.

The CERT/CC has independently confirmed this issue in McAfee VirusScan Enterprise 8.8 patch 7 on Internet Explorer 11 for Windows 7 and reported details to McAfee in June 2016. It is unclear if other versions of Internet Explorer are also affected. The CERT/CC will continue to work with Intel Security/McAfee to address this issue.

This issue was originally published as part of VU#245327, but was later moved to its own Vulnerability Note to prevent product confusion.

Impact

By convincing a user to view a specially crafted HTML document (e.g., a web page or an HTML email message or attachment), an attacker may be able to cause a denial of service.

Solution

The CERT/CC is currently unaware of a practical solution to this problem. However, affected users may consider the following workaround:

Disable the McAfee ActiveX control in Internet Explorer

The vulnerable McAfee ActiveX control can be disabled in Internet Explorer by setting the kill bit for the following CLSID:

    {7DB2D5A0-7241-4E79-B68D-6309F01C5231}

More information about how to set the kill bit is available in Microsoft Support Document 240797. Alternatively, the following text can be saved as a .REG file and imported to set the kill bit for this control:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{7DB2D5A0-7241-4E79-B68D-6309F01C5231}]
    "Compatibility Flags"=dword:00000400
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{7DB2D5A0-7241-4E79-B68D-6309F01C5231}]
    "Compatibility Flags"=dword:00000400

Vendor Information (Learn More)

Vendor Status Date Notified Date Updated
McAfee Affected 08 Jun 2016 19 Dec 2016

If you are a vendor and your product is affected, let
us know
.

CVSS Metrics (Learn More)

Group Score Vector
Base 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C
Temporal 6.1 E:U/RL:U/RC:UR
Environmental 4.6 CDP:ND/TD:M/CR:ND/IR:ND/AR:ND

References

Credit

Thanks to Shelby Kaba for reporting this issue to us.

This document was written by Garret Wassermann.

Other Information

  • CVE IDs:
    Unknown
  • Date Public:
    12 Dec 2016
  • Date First Published:
    13 Dec 2016
  • Date Last Updated:
    19 Dec 2016
  • Document Revision:
    46

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.

Related: