Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

can't copy files from cd rom to harddrive in windows xp

Dec 7, 2003 11:35AM PST

Everytime I try to copy my mp3 files from my cdrom drive to my harddrive in windows xp the machine reboots itself. I am at a loss as to what is causing this. This is a new machine and the drives are from my previous machine. Any advice would be appreciated
Thank You

Discussion is locked

- Collapse -
Re:can't copy files from cd rom to harddrive in windows xp
Dec 7, 2003 9:22PM PST

First of all. tell us more about the machine: Processor Speed, Memory, etc. Then :
How did you copy ? Please give the exact procedure how you did it. Have you had any problems with the computer, and in particular, that CD ROM ? What are the sizes of the MP3 files ? How long are their file names ? How are the " my mp3 files " created ? Many questions, but answers to them may provide clues to a possible solution.

- Collapse -
Re:Re:can't copy files from cd rom to harddrive in windows xp
Dec 8, 2003 9:46AM PST

Hi Papa Echo:
This is an amd athalon 900mhz clone with 512 mb memory. 1 maxtor 20gb harddrive slave 1 maxtor digital 20gb hardrive master on one controller, and two cd/dvd rewritable drives on the second controller. The mother board is an IWill kk266. I have tried the drag and drop method, the copy this folder command in the control panel and the right click copy and paste. Each time the process will start and then the screen goes black and the computer reboots itself. The music is on Cd roms in mp3 format that I downloaded from the internet some time ago. The titles are of various sizes as are the mp3 files themselves. I can play them okay from the cd roms, I just can't copy them to the harddrives. I didn't have any problem copying them from cd rom to a windows 98 machine. Thanks for taking the time to answer.

- Collapse -
New machine = New warranty.
Dec 7, 2003 9:32PM PST

Why not make this problem for the supplier to sort out?

Bob

- Collapse -
Re:New machine = New warranty.
Dec 8, 2003 9:52AM PST

Hi R. Proffitt:
Not an option. This is a bare bones assembly and the supplier is in a different state. I need to figure this out myself.
Thanks for your prompt response.

- Collapse -
'Event' - PART I.
Dec 7, 2003 10:24PM PST

1. The article [Q308427] states that an event is any significant occurrence in the system or in a program that requires users to be notified or an entry be added to one of three logs. The Event Log Service records application, security, and system events in Event Viewer. With the event logs in Event Viewer, users can obtain information about hardware, software, and system components, and monitor security events on a local or remote computer. Event logs can help identify and diagnose the source of current system problems, or help predict potential system problems.

2. The article [Q307973] suggest that a user configure the action as follows that Windows should take when a severe error (also called a fatal system error, or Stop error) occur:

3. The MSDN article [System Error Messages] contains the text of Microsoft

- Collapse -
Re:'Event' - PART II.
Dec 7, 2003 10:25PM PST

a. Even though this article does not specifically address WinXP, I believe you'll find the majority of the error codes and descriptions for them pretty much match and could give you some insight as to the problem to troubleshoot. Simply click the tiny plus before the subject in the left frame and then click on the category containing the series of the error code the system rendered.

b. Access the TechNet Windows XP Events and Errors page and enter the error code to see if anything is rendered.

c. A "list" of event messages by category may be read from this link at the Microsoft TechNet library.

d. Try the Event ID.Net Web site otherwise -- a $15 a year subscription is required.

4. The article [Q314084] describes how to gather more information about an error message that appears on a blue screen. Note that these steps do not always provide conclusive answers and may only point you to another problem. Using Pstat.exe, a Resource Kit utility run from the command line, you are given a picture of the processes and drivers that are currently running. By using the starting address in the "LoadAddr" column, you can match the exception address to the driver name nearest and is most likely the driver that called the exception. With this information, you can go to the MSKB library to look for known issues matching the situation.

- Collapse -
Re:'Event' - PART I.
Dec 8, 2003 9:50AM PST

Thank you for taking the time to answer. I will check the articles.

- Collapse -
Re:Re:'Event' - PART I.
Dec 8, 2003 11:30AM PST

Did you put on the Mainboard drivers?

Try disconnecting all the drives except the boot drive and one CDROM. Try again.

If this works, you may have an underpowered power supply.

Barebones from another state, sounds "cheap".
I'm not knocking your system, but many use 400 watt
$4 power supply units that will barely outperform a
firefly.

My guess is that if the mainboard drivers are installed
and the drives themselves are not defective and are
jumpered correctly, that the PSU is not big enough.

Merl Priester