ExploreZip (also known as I-Worm.ZippedFiles ) is a destructive computer worm that attacks machines running Microsoft Windows . It was first discovered in Israel on June 6, 1999. The worm contains a malicious payload, and utilizes Microsoft Outlook, Outlook Express, or Exchange to mail itself out by replying to unread messages in the user's inbox. The worm also searches mapped drives and networked computers for Windows installations. If found, it copies itself to the Windows folder of the remote computer and then modifies the Win.ini file of the infected computer. On January 8, 2003, Symantec discovered a packed variant of this threat which exhibits the same characteristics.
14-464: The worm is distributed in the form of an e-mail with the words: Hi ! I have received your email and I shall send you a reply ASAP. Till then, take a look at the attached zipped docs. bye The message includes an attachment with the name ZIPPED_FILES.EXE. If opened, a dialog box appears in Windows resembling the one normally appearing when opening a corrupted Zip archive, while
28-410: A dialog box is the about box found in many software programs, which usually displays the name of the program, its version number, and may also include copyright information. Non-modal or modeless dialog boxes are used when the requested information is not essential to continue, and so the window can be left open while work continues elsewhere. A type of modeless dialog box is a toolbar which
42-528: A warning alert box or chicken box) is a dialog box that asks user to approve requested operation. Usually this dialog appears before a potentially dangerous operation is performed (program termination, file deletion, etc.) Typically confirmation dialog boxes have two buttons (e.g. Yes / No , Confirm / Cancel ) or three buttons (e. g. Save / Discard / Cancel ). Some human interface guidelines recommend avoiding unnecessary confirmation dialogs. BlackBerry and Sun Java UI guidelines recommended
56-406: Is a stub . You can help Misplaced Pages by expanding it . Dialog box In computing , a dialog box (also simply dialog ) is a graphical control element in the form of a small window that communicates information to the user and prompts them for a response. Dialog boxes are classified as " modal " or "modeless", depending on whether they block interaction with the software that initiated
70-418: Is either separate from the main application, or may be detached from the main application, and items in the toolbar can be used to select certain features or functions of the application. In general, good software design calls for dialogs to be of this type where possible, since they do not force the user into a particular mode of operation. An example might be a dialog of settings for the current document, e.g.
84-599: Is greyed out, and the dialog appears on top of the middle of the parent window. No work can be done in the underlying document itself while the dialog is displayed, but the parent window can still be moved, re-sized, and minimized, and other windows can be brought in front so the user can work with them: The same type of dialog box can be compared with the "standard" modal dialog boxes used in Windows and other operating systems. Similarities include: The differences are that Both mechanisms have shortcomings: Confirmation dialog box Confirmation dialog (sometimes called
98-507: The background and text colors. The user can continue adding text to the main window whatever color it is, but can change it at any time using the dialog. (This isn't meant to be an example of the best possible interface for this; often the same functionality may be accomplished by toolbar buttons on the application's main window.) System modal dialog boxes prevent interaction with any other window onscreen and prevent users from switching to another application or performing any other action until
112-423: The dangerous action. A modal dialog interrupts the main workflow . This effect has either been sought by the developer because it focuses on the completion of the task at hand or rejected because it prevents the user from changing to a different task when needed. The concept of a document modal dialog has recently been used, most notably in macOS and Opera Browser . These dialogs block only that window until
126-452: The dialog. The type of dialog box displayed is dependent upon the desired user interaction . The simplest type of dialog box is the alert , which displays a message and may require an acknowledgment that the message has been read, usually by clicking "OK", or a decision as to whether or not an action should proceed, by clicking "OK" or "Cancel". Alerts are also used to display a "termination notice"—sometimes requesting confirmation that
140-483: The issue presented in the dialog box is addressed. System modal dialogs were more commonly used in the past on single tasking systems where only one application could be running at any time. One current example is the shutdown screen of current Windows versions. Modal dialog boxes temporarily halt the program: the user cannot continue without closing the dialog; the program may require some additional information before it can continue, or may simply wish to confirm that
154-503: The notice has been read—in the event of either an intentional closing or unintentional closing (" crash ") of an application or the operating system . ( E.g. , " Gedit has encountered an error and must close.") Although this is a frequent interaction pattern for modal dialogs, it is also criticized by usability experts as being ineffective for its intended use, which is to protect against errors caused by destructive actions, and for which better alternatives exist. An example of
SECTION 10
#1732780819920168-415: The user dismisses the dialog, permitting work in other windows to continue, even within the same application. In macOS , prior to macOS Big Sur , dialogs appear to emanate from a slot in their parent window, and are shown with a reinforcing animation. This helps to let the user understand that the dialog is attached to the parent window, not just shown in front of it. In Big Sur and later, the parent window
182-431: The user wants to proceed with a potentially dangerous course of action ( confirmation dialog box ). Usability practitioners generally regard modal dialogs as bad design-solutions, since they are prone to produce mode errors . Dangerous actions should be undoable wherever possible; a modal alert dialog that appears unexpectedly or which is dismissed automatically (because the user has developed a habit ) will not protect from
196-611: The worm copies itself onto the machine's hard drive. It also modifies the WIN.INI file ( Windows 9x ) or the Windows Registry ( Windows NT ) so that it re-executes on reboot . The worm looks for a copy of Microsoft Outlook to mail itself to all other people in the user's address book . It then destroys Microsoft Office documents, C , C++ , and assembly language source files on the user's hard drive by overwriting them with zero-byte files. This malware -related article
#919080