D kan læse denne her smøre:
dette er ikke til win2000 men til windows NT4 men burde fungere også
på dit system !!!
Held og lykke
Thomas
Adobe
part 1
############################################################################
#####################
Status:
Number:
Last Revision:
Active
323908
Fax: 323908
05/24/2000
Troubleshooting Windows NT 4.0 System Errors in InDesign, Part One
What\'s Covered
Getting Started
Troubleshooting Procedures
What to Do Next
This document can help you identify and prevent system errors that
you receive while using Adobe InDesign in Windows NT. System errors can
manifest themselves in many different ways, including (but not limited to)
the following:
- \"An application error has occurred.\"
- \"Unhandled exception.\"
- \"Illegal Instruction.\"
- \"Exception: Access Violation.\"
- Any reference to \"Dr. Watson.\"
- Blank or flickering dialog boxes
Although a system error may appear to occur only with InDesign,
InDesign may not necessarily be the cause. For example, InDesign may be the
only application on your system that is memory-intensive enough to trigger a
system error. Many factors can cause system errors, including conflicts
among device drivers, software, and hardware, and corrupt elements in
specific files.
If you have questions about this document or need additional help,
contact Adobe Technical Support at 206-675-6311.
Getting Started
Before you perform the troubleshooting procedures in this document,
consider these questions:
- Has the error always occurred? If not, when did it start
occurring?
- Has anything changed on the computer before the error first
occurred?
Your answers to these questions can help you quickly determine
possible causes of the error. If the error has always occurred, something
already set on your system --- such as improperly installed files --- could
be the cause. If the error suddenly started occurring, the cause may be too
little disk space or a recent change to your system.
You should also see if you can consistently re-create the error or
freeze: Does it happen when you perform a specific set of actions, such as
printing, saving, or closing documents? If you can\'t consistently re-create
the problem, you should run the system and InDesign long enough after you
perform a troubleshooting procedure to ensure that the error is resolved. If
no error occurs, the troubleshooting procedure probably resolved it. To
determine whether an error is repeatable, keep a record of all the errors
you encounter, including the exact messages, which applications were open at
the time the error occurred, and the actions you performed just before the
error occurred.
We suggest that you back up important documents and any third-party
plug-ins or user dictionaries (*.udc files). Though the procedures in this
document are relatively low-risk, you may feel more secure if you back up
the hard disk as well. Backing up the hard disk is always a good idea before
you make changes to the system. You can use Windows NT Explorer or a
commercial backup program (e.g., Symantec\'s Norton Utilities) to copy files
from a hard disk to another hard disk, a tape drive, a series of disks, or
another form of removable media (e.g., Zip disk or Jaz disk).
Resources You Will Need
Before you begin a procedure, make sure that you have the materials
and time required to do it properly. You will need the following items to
complete all the procedures in this document:
- Windows NT CD-ROM (and Service Pack 4 or later)
- Adobe InDesign CD
- Virus detection software
- Adobe InDesign User Guide
- Internet access
Showing Filename Extensions
Some of the following procedures require that you log in as
Administrator or as a user who has administrative rights. Further, some of
these procedures require you to look for files with specific filename
extensions (e.g., filename.tmp). By default, Windows NT Explorer hides
filename extensions it recognizes.
To display all filename extensions in Windows NT Explorer:
1. Choose Start > Programs > Windows NT Explorer.
2. Choose View > Options (or Folder Options).
3. Click the View tab in the Options dialog box.
4. Select Show All Files.
5. Deselect Hide File Extensions for Known Files and click OK.
Troubleshooting Procedures
The tasks in this section will help you isolate the most common
causes of system errors that occur frequently and with more than one file.
Before performing any of these tasks, make sure to back up all personal
files (e.g., InDesign image files you created, third-party plug-ins).
A. Make sure that your system meets the minimum requirements for
InDesign.
Check that your system meets the following requirements for
InDesign:
- Intel Pentium II processor (Intel Pentium II 300 mHz or faster
processor is recommended) *
- Windows NT 4.0 or later with Service Pack 4 **
- 48 MB of RAM available to InDesign (64 MB recommended)
- 75 MB of available hard-disk space for minimum installation
- CD-ROM drive
- Video card that supports 256 colors at 800x600 monitor resolution
- For PostScript printers: Adobe PostScript Level 2 or higher
* Although InDesign has been tested only with Intel processors, many
of our customers work successfully in InDesign using Intel-compatible
processors (e.g., Cyrix, Newgen, or AMD).
** To check which Service Pack is installed, choose Start > Run,
type \"winver\" in the Open text box, and then click OK.
Note: In addition to the hard-disk space for installation, InDesign
requires space on the startup disk for working in documents. Make sure that
free disk space equals three to five times the size of all open documents,
including any linked graphics.
B. Re-create the InDesign preference files.
InDesign\'s preference files store application-level defaults, such
as default font and page size. If a preference file becomes corrupted, it
can cause errors in InDesign.
Note: If you re-create the InDesign preference files, custom
settings will be lost. InDesign stores a separate set of preferences files
for each user. If you share your computer with other users, make sure that
you delete only the preferences files stored in your user profile (i.e.,
Winnt\\Profiles\\[your username]).
To re-create the InDesign preference files:
1. Exit from InDesign.
2. Choose Start > Find > Files or Folders.
3. Type \"InDesign SavedData\" with the quotes in the Named field.
4. From the Look In pop-up menu, choose the drive on which InDesign
is installed.
5. Click Find Now.
6. Select the preference file in the Find window and choose File >
Delete.
7. Type \"InDesign Defaults\" with the quotes in the Named field and
repeat steps 4-6.
8. Restart InDesign. InDesign automatically re-creates the
preference files.
C. Move documents, graphics, and fonts to a local hard disk.
If you work on InDesign documents stored on a network or removable
media such as an Iomega Zip or Jaz drive, move the documents, graphics, and
fonts to a local hard disk before using them. Network interruptions or write
errors caused by disconnection of a network volume or removable media can
cause transmitted data to be incomplete, lost, or corrupt, resulting in
possible damage to your document.
For more information, see document 322379, \"InDesign, Networks, and
Removable Media.\"
D. Close other applications when working in InDesign.
To make more memory available and to identify whether InDesign is
conflicting with other software, exit from all applications before you work
in InDesign and disable background applications and utilities (i.e., items
that load automatically in Windows NT).
To disable background applications and utilities, remove them from
the two Startup folders:
1. Exit from all applications.
2. Choose Start > Programs > Windows NT Explorer.
3 Move all icons and shortcuts from the Winnt\\Profiles\\[Current
User]\\Start Menu\\Programs\\Startup folder to another folder.
4. Move all icons and shortcuts from the Winnt\\Profiles\\All
Users\\Start Menu\\Programs\\Startup folder to another folder.
5. Restart Windows and try to re-create the error:
- If the error recurs, go to step 6.
- If the error does not recur, isolate the startup item that caused
the error: Move each item, one at a time, back to its Startup folder and try
to re-create the error after moving each item. If you can re-create the
error after moving an item to a Startup folder, permanently remove that item
from the Startup folder.
6. Open the Registry Editor by choosing Start > Run, typing
\"regedit,\" and clicking OK.
Disclaimer: The Windows registry contains system-related information
that is critical to your computer and applications. Before you modify the
registry, be sure to make a backup copy of it. Adobe does not provide
support for problems that arise from improperly modifying the registry.
Adobe strongly recommends that you have experience editing system files
before you modify the registry. For information on the Windows Registry
Editor, see the Windows User Guide or contact Microsoft Technical Support.
7. Select the
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run key and
choose Registry > Export Registry File.
8. Name the file (e.g., HLMrun.reg) and save it to the desktop.
9. In the Registry Editor, make sure that the key is still selected
and choose File > Delete.
10. Select the
HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run key and
choose Registry > Export Registry File.
11. Name the file (e.g., HCUrun.reg) and save it to the desktop.
12. In the Registry Editor, make sure that the key is still selected
and choose File > Delete.
11. Choose File > Exit to close the Registry Editor and then restart
your computer.
If the error recurs after deleting the Run keys, the Run keys are
not the cause of the error. You can restore these keys by double-clicking
the exported files that you saved to the desktop.
E. Update the video driver.
Contact the computer or video card manufacturer to see if an updated
video driver is available. (Many manufacturers frequently update their
drivers.) In the meantime, you may encounter fewer problems by changing your
video settings.
To change the video settings:
1. Choose Start > Settings > Control Panel.
2. Double-click Display and click the Settings tab.
3. Change the Color Palette to 256 colors. If it\'s already at 256
colors, change it to High Color or True Color. (True Color may be designated
as 24-bit color, 16,777,216 colors, or millions of colors).
4. Change the Desktop Area setting. For example, if it is set to
1024x768, try 800x600.
5. Click Test and follow the on-screen instructions.
6. When the test screen appears, click Apply to make the change.
7. Click OK.
8. Restart Windows and then InDesign. If changing the video settings
does not fix the problem, you can restore the original settings.
F. Make sure that the system has a valid temporary folder with
sufficient hard disk space available to it.
Windows NT, InDesign, and other Windows applications use temporary
(*.tmp) files to store changes made to files since they were last saved and
to spool information for printing. InDesign also creates temporary files
when it starts and when you open, create, or print InDesign documents. If
hard disk space is insufficient for these temporary files, a system error
may occur. As a guideline, have 10% of your total hard disk capacity
available for temporary files.
To determine where InDesign writes its temporary files when it
starts or prints, choose Start > Settings > Control Panel, and select the
Environment tab. Locate the TMP line in the User Variables section (if it
exists). Note the drive letter and folder name in the Value column (e.g.,
C:\\Temp). This folder is where Windows stores most temporary files. If the
Value column lists \"%SystemDrive%,\" Windows stores temporary files on the
same hard drive on which the Winnt folder resides.
InDesign also stores special temporary files in the Program
Files\\Adobe\\InDesign\\InDesign Recovery folder. When InDesign performs
\"mini-saves\" (i.e., saves between those requested by the user), it stores
changes in temporary files. The data contained in these temporary files are
incorporated into the original document when you choose File > Save or when
you open a document after an application or system crash. This process makes
it possible to recover data more recent than that in the last saved version
of a file.
To ensure that enough space is available for temporary files, open
Windows NT Explorer and select the disk that contains the Temp folder. The
free disk space appears at the bottom of the Explorer window. (If the disk
space does not appear at the bottom of the window, choose View > Status Bar
from within the Explorer window and make sure that Status Bar is checked.)
If the hard disk does not have enough free space, you can free more
space by deleting unnecessary temporary files. Most applications delete
their temporary files when you exit from the application. When the system
freezes or applications quit unexpectedly, however, temporary files may
remain on the system.
To delete temporary files:
1. Exit from all applications.
2. Choose Start > Find > Files or Folders.
3. In the Named text box, type \"*.tmp\" (without the quotes).
4. Choose Local Hard Drives from the Look In pop-up menu. (Some
applications write temporary files to hard drive partitions and folders
other than the designated ones.)
5. Click Find Now.
6. When the search results appear, choose Edit > Select All.
7. Choose File > Delete. Click Yes to send the files to the Recycle
Bin.
8. Check the Recycle Bin for any non-temporary files you do not want
to delete, and remove them if desired.
9. Empty the Recycle Bin. Windows NT can not delete temporary files
that are still in use. Instead, it returns the error, \"Cannot delete
[filename]: Access denied.\" If Windows NT returns this error, click OK and
then deselect the file noted in the error by pressing the Ctrl key and
clicking the filename.
If you still do not have enough free disk space after deleting
temporary files, you can edit or add the TMP user variable using the
Environment tab of the System Control Panel to specify a folder on a
non-compressed hard drive that has enough free space. Remember, however,
that the location of the recovery folder that InDesign uses cannot be
changed.
Note: Check with your system administrator before editing or adding
a TMP variable. You may need Administrator access.
To edit or add the TMP variable:
1. Choose Start > Settings > Control Panel, double-click System, and
click the Environment tab.
2. Check for the TMP variable in the User Variables section:
- If the TMP variable does not exist, type \"TMP\" in the Variable
text box.
- If the TMP variable exists, select the variable name.
3. In the Value text box, type a path to a hard disk that contains
at least 100 MB of free disk space (e.g., D:\\Temp).
4. In Windows NT Explorer, verify that the drive and folder exist.
If the drive does not exist, choose another drive. If the folder does not
exist, create it by selecting the drive, choosing File > New Folder, and
then naming the folder \"Temp\".
6. Click Set and then click OK.
7. Restart Windows.
G. Adjust the Windows NT virtual memory settings.
InDesign uses the Windows NT paging file (or files) to perform
virtual memory functions. If the computer has less than 128 MB of installed
RAM, adjust the virtual memory settings to use a paging file that is 2-3
times the amount of installed RAM. If the computer has more than 128 MB of
installed RAM, use the default virtual memory settings.
To adjust the virtual memory settings:
1. Exit from all applications.
2. Choose Start > Settings > Control Panel.
3. Double-click System and click the Performance tab.
4. Click Change in the Virtual Memory section.
5. From the Drive list, select a hard disk that has free space equal
to at least twice the amount of the computer\'s installed RAM. For example,
if the computer has 48 MB of RAM, select a hard drive that has at least 96
MB of free hard disk space.
6. In the Initial Size field, enter a value equal to the amount of
the computer\'s installed RAM plus 12 MB.
7. In the Maximum Size field, enter a value equal to twice the
amount of the computer\'s installed RAM.
8. Click Set and then click OK.
9. Click OK to close the System Properties dialog box.
10. To restart Windows, click Yes in the System Settings Change
dialog box.
H. Use a disk utility to repair the hard disk.
System errors can occur if there are damaged sectors on the hard
disk. You can diagnose and repair disk errors by using the Windows NT Check
Disk utility or a utility such as Norton Utilities Disk Doctor.
To use Check Disk:
1. Choose Start > Programs > Windows NT Explorer.
2. Right-click the hard disk icon and then choose Properties.
3. Select the Tools tab and click Check Now.
4. Select Automatically Fix Errors in the Check Disk dialog box.
5. Click Start. The process may take a while if the hard disk
contains a lot of data or has a lot of errors. Check Disk may appear to
restart repeatedly; this is normal.
I. Remove and reinstall InDesign.
Remove InDesign and then reinstall it from the CD while Windows is
in VGA mode with no other applications running. Reinstalling InDesign
ensures that the InDesign application and its resource files are not
damaged. Because the InDesign installer will not replace files that are
already present, you must remove InDesign before reinstalling it.
To remove and reinstall InDesign:
1. Move any personal files (e.g., images, third-party plug-ins) out
of the InDesign folder and its subfolders.
2. Choose Start > Settings > Control Panel, double-click Add/Remove
Programs, select Adobe InDesign, and then click Add/Remove. If the InDesign
folder still exists after uninstalling, delete it and its subfolders.
3. Delete the following folders, where \"X\" is the hard drive on
which InDesign was installed:
- X:\\Winnt\\Profiles\\[your username]\\Local Settings\\Application
Data\\Adobe\\InDesign
- X:\\Program Files\\Common Files\\Adobe\\Web
4. Disable all background applications and utilities. For
instructions, see procedure D.
5. Restart Windows NT 4.0 and choose Windows NT Workstation Version
4.00 [VGA Mode] from the boot loader screen. Starting Windows NT 4.0 in VGA
mode temporarily replaces the video driver with the Windows NT 4.0 standard
VGA driver and can prevent video conflicts with the installation.
Note: If the boot loader screen doesn\'t appear or flashes by too
quickly, choose Start > Settings > Control Panel, double-click System, and
click the Startup/Shutdown tab. Choose Windows NT 4.0 Workstation Version
4.00 [VGA Mode] from the Default Operating System pop-up menu and restart
the computer.
6. Insert the InDesign CD and from the Autoplay window, click Adobe
InDesign. If the Autoplay window does not appear, select the CD-ROM drive in
Windows NT Explorer, double-click the InDesign folder, and then double-click
the Setup.exe file. If other problems occur when you install InDesign, see
document 324052, \"Error or Freeze When Installing InDesign 1.0 in Windows\"
or 325131, \"Freeze or Error When Installing InDesign 1.5 in Windows.\"
7. After you install InDesign, restart Windows NT in normal mode. If
the boot loader screen doesn\'t appear or flashes by too quickly, choose
Start > Settings > Control Panel, double-click System, and click the
Startup/Shutdown tab. Choose Windows NT 4.0 Workstation Version 4.00 from
the Default Operating System pop-up menu and restart the computer.
What to Do Next
By completing the procedures in this document, you have eliminated
the causes of most system errors and have reduced the likelihood of other
system problems. If the error persists after thoroughly completing these
procedures, its cause is probably something more complex or obscure than
these procedures could identify.
To continue troubleshooting, complete the more complex procedures in
document 323911, \"Troubleshooting Windows NT 4.0 System Errors in InDesign,
Part Two.\" You can get it from the Technical Solutions Database on Adobe\'s
Web site at
www.adobe.com. If you need troubleshooting assistance, contact Adobe Technical
Support at 206-675-6311. Please have a record of the errors you\'ve received
and procedures you\'ve completed when you call.
Related Records
Troubleshooting Windows NT 4.0 System Errors in InDesign, Part Two
Further Reading
Sources
part 2
############################################################################
#####################
Status:
Number:
Last Revision:
Active
323911
Fax: 323911
05/24/2000
Troubleshooting Windows NT 4.0 System Errors in InDesign, Part Two
What\'s Covered
Getting Started
Troubleshooting Procedures
Further Troubleshooting Suggestions
Resources
This document is the second of two troubleshooting documents designed to
help you resolve system errors that you receive while using Adobe InDesign
in Windows NT. The troubleshooting procedures listed in the first document
323908, \"Troubleshooting Windows NT System Errors in InDesign, Part One,\"
resolve most system errors and are easier to perform than those listed here.
If you complete the procedures in the first document and still receive
system errors, use this document to continue troubleshooting. The procedures
in this document are those that Adobe Technical Support uses to resolve more
complicated system errors. Some of the procedures may seem similar to those
in the first document, but they are covered more thoroughly in this
document. System errors may recur even after you complete all the procedures
in both documents. However, completing these procedures lets you determine
which variables are not causing the problem, so you can focus on the
variables that remain.
Getting Started
The procedures in this document may be awkward or inconvenient. For that
reason, make sure that you have the time and flexibility to complete them.
To determine whether a procedure resolves an error, you must be able to work
long enough to be sure that the error doesn\'t recur. Before you make any
changes to the system, back up the hard disk, especially important files,
and gather the resources listed below.
Using a System Error Log
As you work through these procedures, use a system error log, such as the
one available on Adobe\'s Web site at
www.adobe.com/support/pdfs/ts_log.pdf.Use the log to document errors that occur and troubleshooting procedures you
perform. Be as accurate and thorough as possible. A log can help you
identify trends, saving you considerable time in the troubleshooting
process. For example, if an error always occurs when you work with text, the
cause is likely to be a font or font management utility.
Keep the log next to the computer and make sure that everyone who uses the
computer records any system errors they receive, no matter which application
they are using at the time. Record the exact system error, the applications
that are open at the time the error occurs, and the action that was most
recently completed. And, make sure that you have the log handy if you call
Adobe Technical Support for assistance.
Resources You Will Need
- Windows NT 4.0 CD and Service Pack 4.0 or later
- Installation CDs or disks for applications you may need to
reinstall (e.g., InDesign, Microsoft Word)
- Original font installation CDs or disks
- Installation disks for drivers and utilities (e.g., printer
drivers)
- Internet access
- System Error Log, available on Adobe\'s Web site at
www.adobe.com/support/pdfs/ts_log.pdf Troubleshooting Procedures
Complete these procedures after completing procedures A-I in document
323908, \"Troubleshooting Windows NT 4.0 System Errors in InDesign, Part
One.\"
J. Install the latest service pack for Windows NT.
Service packs improve the operating system and increase compatibility with
other applications. Installing the latest service pack can resolve errors
related to the version of system software. Windows NT service packs are
available from Microsoft\'s Web site at
www.microsoft.com/windows/downloads. Note: If Windows NT was preinstalled on your computer, contact the computer
manufacturer to determine which updates you need.
K. Specify a different printer as your default printer.
Windows may return errors if InDesign conflicts with the default printer or
if the driver for the default printer is damaged. To determine if a problem
exists with the current printer driver, try specifying a different default
printer.
If only one printer is installed, you can install a PostScript printer
driver using the Adobe PostScript (AdobePS) Setup Utility for Windows NT,
which is available from Adobe\'s Web site at
www.adobe.com/support/downloads/pdrvwin.htm, or you can install a
non-Postscript printer driver (e.g., Hewlett-Packard DeskJet) using the Add
Printer wizard in the Printers Control Panel. You do not need to have a
printer attached to your computer to install a driver for it.
To specify a printer as the default printer:
1. Choose Start > Settings > Printers.
2. Right-click a printer (other than the current default printer),
and then choose Set as Default.
L. Check for font problems.
InDesign accesses font information when it starts, formats text, redraws a
page, or prints a publication. If a font file is damaged, or if too much
font information has been written to the Windows registry, the system may
return an error.
To determine if an problem is font-related, remove all fonts except those
installed by Windows NT:
1. Disable font utilities (e.g., Adobe Type Manager [ATM] or Ares
FontMinder). For instructions, see the documentation for the utilities.
2. Close all applications, and then right-click the desktop and
choose New > Folder from the pop-up menu.
3. Name the folder \"Oldfonts.\"
4. Choose Start > Settings > Control Panel.
5. Double-click the Fonts folder.
6. Select each installed font, except those installed by Windows NT.
(See \"Fonts Installed by Windows NT,\" below.) You can select a contiguous
group of fonts by holding down the Shift key when selecting the first and
last fonts in that group; to select non-contiguous fonts, hold down the Ctrl
key while you select fonts.
7. Move the selected fonts into the Oldfonts folder you created in
step 3.
8. Restart Windows.
Fonts Installed by Windows NT
Note: Windows also installs several hidden font files (e.g.,
Marlett.ttf, Dosapp.fon, and Vgafix.fon), which may not appear in Windows
Explorer or in the Fonts Control Panel. Windows requires these hidden font
files to run. Do not delete or move them.
Font
Filename
Arial
Arial.ttf
Arial Bold
Arialbd.ttf
Arial Bold Italic
Arialbi.ttf
Arial Italic
Ariali.ttf
Courier 10,12,15
Courf.fon
Courier New
Cour.ttf
Courier New Bold
Courbd.ttf
Courier New Bold Italic
Courbi.ttf
Courier New Italic
Couri.ttf
Lucida Console
Lucon.ttf
Modern
Modern.fon
MS Sans Serif 8, 10, 12, 14, 18, 24
Sseriff.fon
MS Serif 8, 10, 12, 14, 18, 24
Seriff.fon
Roman
Roman.fon
Script
Script.fon
Small Fonts
Smallf.fon
Symbol
Symbol.ttf
Symbol 8, 10, 12, 14, 18, 24
Symbolf.fon
Times New Roman
Times.ttf
Times New Roman Bold
Timesbd.ttf
Times New Roman Bold Italic
Timesbi.ttf
Times New Roman Italic
Timesi.ttf
WingDings
Wingding.ttf
If the problem recurs after you remove the fonts, it is probably not
font-related. If, however, the problem does not recur after you remove the
fonts, follow the instructions in document 321430, \"Troubleshooting Font
Problems in Windows.\"
M. Check for viruses.
Use current anti-virus software (e.g., Norton AntiVirus or McAfee AntiVirus)
to check the system for viruses. Although virus infections are rare, they
can cause system errors. Running virus detection software regularly (e.g.,
daily) prevents viruses from damaging software on your system. Virus
detection software manufacturers release updated virus definitions
regularly; using the most recent definitions gives you greater protection
against new viruses. For instructions on running your virus detection
software or obtaining updated virus definitions, see the documentation for
the anti-virus software.
N. Use Event Viewer to check for system problems.
The Windows NT Event Viewer reports system problems such as damaged files or
drivers that failed to start or load.
To use Event Viewer:
1. Choose Start > Programs > Administrative Tools (Common) > Event
Viewer.
2. Choose Log > System.
3. Double-click any lines with a red stop sign or an exclamation
mark in a yellow circle for a description of the event. If you are unable to
determine what the events mean or how to resolve them, contact Microsoft
Technical Support.
Note: If you find it hard to determine what events relate to your error
message, start a fresh system log. In the Event Viewer, choose Log > Clear
All Events, and save the events in a file when prompted. Then attempt to
re-create the error and view the system log.
O. Eliminate duplicate system files.
Duplicate system files can cause erratic behavior with Windows and
applications (e.g., hard disk problems or conflicts with third-party
utilities). Different applications may load different versions of system
files. Make sure that only one copy exists for each Windows system file
(e.g., Win.com, System.ini, and Win.ini) and each driver (*.drv) file on
your computer. You can use Windows Explorer to search each hard disk for
these files; you can sort the search results by name to make it easier to
find duplicates. Rename any duplicates and then restart Windows. For
assistance determining which files to rename, contact Microsoft Technical
Support or your hardware manufacturer.
Note: If you have a dual-boot system (e.g., another copy of Windows NT or
another operating system installed on the same computer), you should have
multiple system files. However, you should have only one copy for each
configuration -- make sure that they are installed in the correct locations.
For more information about configuring a dual-boot system, see your Windows
documentation or contact Microsoft Technical Support.
P. Reinstall the system software and then reinstall InDesign in Windows NT
VGA mode.
The system software is the basic set of files the computer requires to run.
To ensure that a problem is not caused by damaged system software, perform a
clean installation of the system software and all appropriate updates --
that is, replace the existing system software entirely. After you reinstall
the system software, including Service Pack 4 or later, restart Windows NT
in VGA mode and install only InDesign. Installing InDesign while Windows is
running in VGA mode ensures that the video driver does not conflict with the
installation.
Note: You should uninstall InDesign before reinstalling it, since the
InDesign installer does not replace files that are already present and
potentially damaged.
If the problem does not recur with just Windows NT and InDesign installed,
it is most likely software related. Gradually reinstall fonts, applications,
and drivers to isolate those that conflict with InDesign.
If this procedure does not resolve the problem, you may need to reformat the
hard disk and reinstall the system software. You may find it easier to
reformat the hard disk before reinstalling Windows. (Reformatting the hard
disk erases all files on the disk; erased files are irrecoverable.) Before
reformatting the hard disk, make sure to back up files you want to keep.
However, don\'t back up the hard disk and restore Windows and InDesign
instead of performing a clean installation. If the problem is caused by an
application or Windows, and you simply restore both instead of reinstalling
them, the problem may recur.
For assistance reformatting the hard disk and reinstalling Windows, contact
Microsoft or the computer manufacturer.
Further Troubleshooting Suggestions
If the problem still occurs after you\'ve completed these troubleshooting
procedures, it is most likely hardware-related. Before you make changes to
hardware, review your computer warranty and ownership information. If you
are unsure about how to perform any of the procedures below, or if a
warranty prevents you from performing them yourself, contact the
manufacturer or support provider for assistance. Make sure that you have
your completed system error log handy so you can inform the manufacturer or
support provider about the errors you\'ve experienced and what you\'ve done to
troubleshoot the problem.
Make sure that all device drivers and hardware are compatible with Windows
NT 4.0.
Incompatible or outdated drivers or devices can create system problems.
Contact the device manufacturer to make sure that you are using the latest
driver. To make sure that hardware is certified as Windows NT compatible,
consult the Windows NT Hardware Compatibility List at
www.microsoft.com/hcl.Disable hard disk compression on NTFS-formatted drives.
Hard disk compression can interfere with InDesign\'s ability to store and
access files and document resources. To disable disk compression for hard
disks or specific folders, check the Windows NT documentation.
Run the computer with a different RAM configuration.
All software on the computer performs functions in RAM. Damaged RAM modules
can cause system errors. Sometimes errors can be resolved if RAM modules
(e.g., SIMMs or DIMMs) are removed, rearranged, or replaced, even if the
modules aren\'t damaged. Many computers require proprietary RAM modules or
RAM modules of a particular speed. If the RAM modules installed are
incompatible with your computer, the system may not recognize all the RAM or
errors may occur.
Some utilities (e.g., Touchstone Software\'s Wincheckit) can test RAM for
damage, although they may not detect all problems. To determine whether a
particular RAM module is causing the problem, ask your hardware vendor to
remove all but the minimum amount needed to run Windows and InDesign and
test to see if the problem persists. If it does, replace the modules you
removed and then remove others, testing again to see if the problem
persists. If the problem does not recur, one or more of the removed modules
are the cause.
Determine whether the problem is caused by a non-Intel processor.
InDesign was not extensively tested with non-Intel processors (e.g., AMD,
Newgen, or Cyrix). If your computer has a non-Intel processor, and you have
performed all of the above steps and the problem still occurs, the cause may
be an incompatible processor. Contact the computer manufacturer for help
determining whether the processor is conflicting with InDesign.
Investigate other variables in your computing environment.
Other variables unique to your system can cause system errors. In rare
cases, system errors can be caused by SCSI cards, network cards, faulty
motherboards, or other hardware components. Other variables include
environmental factors, such as overheating, power surges, static
electricity, burnouts, electrical interference, dust in the components,
server or cable problems, a faulty battery, or damaged power supply. The
resources listed below can help you identify error-causing factors in your
computing environment.
############################################################################
#####################
Ny bruger
Nybegynder
Opret
Preview
