"You do not have access" for System State Backup

[Guest]

I am registered as Administrator for my stand-alone computer, using Windows
2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System State].
On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk, so I'm
using a rewritable CD in drive E. I changed the drive letter from A: to E:

 

[Mark V]

In microsoft.public.win2000.registry =?Utf-8?B?YmlsbG1hcnRpbjQ0?=
wrote:

I am registered as Administrator for my stand-alone computer,
using Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk,
so I'm using a rewritable CD in drive E. I changed the drive
letter from A: to E:
.
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not the System State.
What should I do to allow the System State backup?

Suggest you backup to a file (.BKF) hard disk, then copy the file to
UDF or burn it to CD-RW. I don't think this is a registry issue.

 

[Jim Byrd]

Hi Bill - Backup doesn't work directly with CD-RW. You can backup to disk
and then copy it over as Mark suggested, or you can try the following
approach AT YOUR OWN RISK courtesy of Mr. Petrus in a posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user way back
in Aug of 2001. I haven't tried this, so I can't verify whether it works or
not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it does not,
add manually by choosing [Add a new device]. Select [No, I want to select
hardware from a list]. Select hardware type as Network adapters. Choose
Microsoft as the manufacturer and 'Microsoft Loopback Adapter' as the
device.

Once installed, right click the CDRW, select properties, then sharing, and
enter a name for the device without any spaces in it. You may need to use
your CDRW software (e.g., Adaptec DirectCD, etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the CDRW as
the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the bottom of
the window that asks you to define the 'Backup media or file name': Do not
select your CDRW but choose the network device you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

 

[Guest]

Jim, Thank you for your help and advice. Your instructions were quite good
and every step seemed to proceed as expected.

When I got to the last step - actually writing onto the renamed rewritable
CD drive, that writing began perfectly. Then it paused because it was unable
to copy one file onto the CD. I clicked OK and it resumed, only to stop at
another file it had some sort of trouble with.
I decided the Backup CD was probably incorrect by now and never going to be
able to restore my System State, should I ever need to. So the next time it
stopped and the screen gave me an option to quit, I did so.
Then the rewritable E: drive became inoperable so I used Ctl-Alt-Del to get
out - and it wouldn't close the drive. Repeated trys failed to close the E:
drive so I finally shut off the computer.
Took forever to shut down, so something was really messed up.
Maybe the new Network Place for the renamed E drive had something to do with
it. I guess we'll never know.

Apparently Windows2000 Professional is just not going to copy my System
State data to a rewritable drive, no matter what trick I try.

Jim, thanks again for a good try.

-Bill Martin Denver, CO

Hi Bill - Backup doesn't work directly with CD-RW. You can backup to disk
and then copy it over as Mark suggested, or you can try the following
approach AT YOUR OWN RISK courtesy of Mr. Petrus in a posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user way back
in Aug of 2001. I haven't tried this, so I can't verify whether it works or
not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it does not,
add manually by choosing [Add a new device]. Select [No, I want to select
hardware from a list]. Select hardware type as Network adapters. Choose
Microsoft as the manufacturer and 'Microsoft Loopback Adapter' as the
device.

Once installed, right click the CDRW, select properties, then sharing, and
enter a name for the device without any spaces in it. You may need to use
your CDRW software (e.g., Adaptec DirectCD, etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the CDRW as
the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the bottom of
the window that asks you to define the 'Backup media or file name': Do not
select your CDRW but choose the network device you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

I am registered as Administrator for my stand-alone computer, using
Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System State].
On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk, so
I'm using a rewritable CD in drive E. I changed the drive letter
from A: to E: .
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E: but
not
the System State.
What should I do to allow the System State backup?

 

[Guest]

Mark, many thanks for your advice.
I did as you said and everything seemed to be according to plan. The file I
had created on my hard drive was apparently written to the CD.
The screen showing the time remaining finally got down to 5 seconds....and
stayed there for 10 minutes.
I concluded that something had gone wrong, so I used the dialog box option
to end the process.
But then I couldn't retreive the rewritable CD in E drive because the screen
said the copy process had been unable to finish and unable to lock the file.
I eventually used Ctl-Alt-Del and retrieved the CD. Then I tried to open the
CD in MS Word2000 so I could compare it to the file on the hard drive. But
the screen display was only little squares and pieces of words, so I couldn't
read it.

I suspect I did not create a valid backup. Maybe Windows2000 Professional
simply won't be tricked into backing up to a rewritable CD.

Mark, thak you again for the advice. We almost made it.

-Bill Martin Denver, CO

In microsoft.public.win2000.registry =?Utf-8?B?YmlsbG1hcnRpbjQ0?=
wrote:

I am registered as Administrator for my stand-alone computer,
using Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk,
so I'm using a rewritable CD in drive E. I changed the drive
letter from A: to E:
.
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not the System State.
What should I do to allow the System State backup?

Suggest you backup to a file (.BKF) hard disk, then copy the file to
UDF or burn it to CD-RW. I don't think this is a registry issue.

 

[Jim Byrd]

Hi Bill - Well, first YW, of course. However, I'm sorry that approach
didn't work for you, but I do appreciate the feedback. I may have to try it
myself just to check. The fact that you had errors when writing
would imply to me that you either have issues with your CD Drive (do you
have such write errors using a normal CD write program such as Easy CD
Creator or Nero?) or possibly a system incompatibility in your ASPI drivers.
You can get ASPIChk and the latest drivers (4.71 I think?) here:
http://www.adaptec.com/worldwide/su...sess=no&language=English+US&prodkey=ASPI-4.70

IIRC, Nero also provides updated ASPI drivers.

You might also want to check whether you have the most current firmware for
your CD RW drive. You can download LiveUpdate from this site to check
that: http://www.drvupdate.com/ Direct download here:
http://www.drvupdate.com/liveupdate/setup/LiveUpdateSetup.exe

"The LiveUpdate Program is a smart tool that enables you to upgrade your
drive's firmware automatically. Through this powerful tool, your drive will
always be optimized for performance and compatibility with the lastest
media."

I've never had a problem with it, but again, use AT YOUR OWN RISK (since it
concerns firmware). Read and follow the User's Guide carefully.


Or you may just want to forget the whole thing.


--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, Thank you for your help and advice. Your instructions were quite
good and every step seemed to proceed as expected.

When I got to the last step - actually writing onto the renamed
rewritable CD drive, that writing began perfectly. Then it paused
because it was unable to copy one file onto the CD. I clicked OK and
it resumed, only to stop at another file it had some sort of trouble
with.
I decided the Backup CD was probably incorrect by now and never going
to be able to restore my System State, should I ever need to. So the
next time it stopped and the screen gave me an option to quit, I did
so.
Then the rewritable E: drive became inoperable so I used Ctl-Alt-Del
to get out - and it wouldn't close the drive. Repeated trys failed
to close the E: drive so I finally shut off the computer.
Took forever to shut down, so something was really messed up.
Maybe the new Network Place for the renamed E drive had something to
do with it. I guess we'll never know.

Apparently Windows2000 Professional is just not going to copy my
System State data to a rewritable drive, no matter what trick I try.

Jim, thanks again for a good try.

-Bill Martin Denver, CO

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try the
following approach AT YOUR OWN RISK courtesy of Mr. Petrus in a
posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user
way back in Aug of 2001. I haven't tried this, so I can't verify
whether it works or not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it
does not, add manually by choosing [Add a new device]. Select [No, I
want to select hardware from a list]. Select hardware type as
Network adapters. Choose Microsoft as the manufacturer and
'Microsoft Loopback Adapter' as the device.

Once installed, right click the CDRW, select properties, then
sharing, and enter a name for the device without any spaces in it.
You may need to use your CDRW software (e.g., Adaptec DirectCD,
etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the
CDRW as the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the
bottom of the window that asks you to define the 'Backup media or
file name': Do not select your CDRW but choose the network device
you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

I am registered as Administrator for my stand-alone computer, using
Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk, so
I'm using a rewritable CD in drive E. I changed the drive letter
from A: to E: .
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not
the System State.
What should I do to allow the System State backup?

 

[Mark V]

In microsoft.public.win2000.registry =?Utf-8?B?YmlsbG1hcnRpbjQ0?=
wrote:

Mark, many thanks for your advice.
I did as you said and everything seemed to be according to plan.
The file I had created on my hard drive was apparently written to
the CD. The screen showing the time remaining finally got down to
5 seconds....and stayed there for 10 minutes.
I concluded that something had gone wrong, so I used the dialog
box option to end the process.
But then I couldn't retreive the rewritable CD in E drive because
the screen said the copy process had been unable to finish and
unable to lock the file. I eventually used Ctl-Alt-Del and

I think you have some issues with your CD-RW or drivers or burning
software or discs ....

If you kill the writing-to-a-CD process you *will* be left with junk.
The write must complete without fatal errors. Also as you observed
Windows might hang and not want to shut down. In that event, waiting
a looong time may eventually allow Windows to shut down. YMMV

retrieved the CD. Then I tried to open the CD in MS Word2000 so I
could compare it to the file on the hard drive. But the screen

Well, I'm sorry, but opening binary files in Word is not an option.
Wrong tool. Hazardous to data. Et Cetera.

Most Windows versions contain the FC.EXE program (a command line
program) for comparing files byte for byte. From a CMD prompt try
FC /?

display was only little squares and pieces of words, so I couldn't
read it.

I suspect I did not create a valid backup.

The foremost advice is to enable "Verify" after backup inside
ntbackup. Always. Once a valid .bkf file exists on hard disk all
the other issues most likely are CD related. For one thing try a
brand new quality CD-R disk for a test burn.

Maybe Windows2000
Professional simply won't be tricked into backing up to a
rewritable CD.

Mark, thak you again for the advice. We almost made it.

I am reasonably certain that the backup-to-HD, then copy/burn to CD-R
or CD-RW should work. Done it thousands of times <G>. I think you
need to look for CD hardware and software problems. Disable A-V
real-time monitors during UDF copying perhaps.

I've never tried your original (or Jim's) methods to "burn direct
from ntbackup" though. I would not trust it myself and it would be
*slower* during the actual backup if it did work reliably.

Staying on-topic (registry) are you getting Event Log error messages
relating to the CD? Otherwise, one of the hardware groups may best
serve you for resolving CD/DVD/Windows issues.


[ snipped most prior ]

 

[Mark V]

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try
the following approach AT YOUR OWN RISK courtesy of Mr. Petrus in

[ snipped ]

Hi Jim. Interesting. Though not what I call elegant <G> "Creative" I
guess. <G> Not something I am interested in using, but was most
interested in reading about it.

Best.

 

[Jim Byrd]

Hi Mark - Agreed, "creative" - that's mainly why I hung onto that post in my
files since 2001.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try
the following approach AT YOUR OWN RISK courtesy of Mr. Petrus in

[ snipped ]

Hi Jim. Interesting. Though not what I call elegant <G> "Creative"
I guess. <G> Not something I am interested in using, but was most
interested in reading about it.

Best.

 

[Guest]

Jim, your advice put me on the right track. I did as you said. Downloaded a
new driver.
A bit more below.

Hi Bill - Well, first YW, of course. However, I'm sorry that approach
didn't work for you, but I do appreciate the feedback. I may have to try it
myself just to check. The fact that you had errors when writing
would imply to me that you either have issues with your CD Drive (do you
have such write errors using a normal CD write program such as Easy CD
Creator or Nero?)

After installing my newly-downloaded driver, I transferred a *.txt file and
an *.exe file to a CD on my E: read-write drive. They both transferred just
fine. So I tried backing up an *.exe file and transferring that *.bkf to
CD. Seemed to work just fine.
So, while my luck was running good for a change, I backed up the System
State and transferred that file to CD. Worked perfectly. Almost too
perfectly. Only took 4-5 seconds to transfer a 242MB System State file to
CD. But my computer is an 800mH machine and I think it should have taken
longer. However, reading the CD *.bkf file name properties, it shows exactly
the same file size as the original that I transferred over.
Is there any way I can test that CD System state file?

or possibly a system incompatibility in your ASPI drivers.

Jim, do I have more than one ASPI driver? I only downloaded one Zip file
from the ASPI web site. It has two folders and 18 files in it when unzipped.
Is it likely that some of those are for my read-only and floppy drive as well
as my read-write drive?

You can get ASPIChk and the latest drivers (4.71 I think?) here:
http://www.adaptec.com/worldwide/su...sess=no&language=English+US&prodkey=ASPI-4.70

IIRC, Nero also provides updated ASPI drivers.

You might also want to check whether you have the most current firmware for
your CD RW drive. You can download LiveUpdate from this site to check
that: http://www.drvupdate.com/ Direct download here:
http://www.drvupdate.com/liveupdate/setup/LiveUpdateSetup.exe

My firmware for the read-write CD drive came from my Computer OEM Back-Up
CD. When I ran LiveUpdate, a message box said "There's no device supported
by Live Update on your system".
My read-write drive is a NEC NR-7700A. The ASPI driver I downloaded seemed
to work OK.
Shouldn't I be able to update my firmware as well? My firmware version is
1.01 which sounds like an original version.

"The LiveUpdate Program is a smart tool that enables you to upgrade your
drive's firmware automatically. Through this powerful tool, your drive will
always be optimized for performance and compatibility with the lastest
media."

I've never had a problem with it, but again, use AT YOUR OWN RISK (since it
concerns firmware). Read and follow the User's Guide carefully.


Or you may just want to forget the whole thing.

I'll admit, I DID get pretty discouraged....but thanks to your generous
assistance, Jim, I seem to have gotten that System State file over to CD.
Many thanks for hanging in there with me.

- Bill Martin Denver, CO

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, Thank you for your help and advice. Your instructions were quite
good and every step seemed to proceed as expected.

When I got to the last step - actually writing onto the renamed
rewritable CD drive, that writing began perfectly. Then it paused
because it was unable to copy one file onto the CD. I clicked OK and
it resumed, only to stop at another file it had some sort of trouble
with.
I decided the Backup CD was probably incorrect by now and never going
to be able to restore my System State, should I ever need to. So the
next time it stopped and the screen gave me an option to quit, I did
so.
Then the rewritable E: drive became inoperable so I used Ctl-Alt-Del
to get out - and it wouldn't close the drive. Repeated trys failed
to close the E: drive so I finally shut off the computer.
Took forever to shut down, so something was really messed up.
Maybe the new Network Place for the renamed E drive had something to
do with it. I guess we'll never know.

Apparently Windows2000 Professional is just not going to copy my
System State data to a rewritable drive, no matter what trick I try.

Jim, thanks again for a good try.

-Bill Martin Denver, CO

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try the
following approach AT YOUR OWN RISK courtesy of Mr. Petrus in a
posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user
way back in Aug of 2001. I haven't tried this, so I can't verify
whether it works or not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it
does not, add manually by choosing [Add a new device]. Select [No, I
want to select hardware from a list]. Select hardware type as
Network adapters. Choose Microsoft as the manufacturer and
'Microsoft Loopback Adapter' as the device.

Once installed, right click the CDRW, select properties, then
sharing, and enter a name for the device without any spaces in it.
You may need to use your CDRW software (e.g., Adaptec DirectCD,
etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the
CDRW as the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the
bottom of the window that asks you to define the 'Backup media or
file name': Do not select your CDRW but choose the network device
you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In billmartin44 <[email protected]> typed:
I am registered as Administrator for my stand-alone computer, using
Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk, so
I'm using a rewritable CD in drive E. I changed the drive letter
from A: to E: .
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not
the System State.
What should I do to allow the System State backup?

 

[Guest]

Mark, I used several pieces of your advice as well as several of Jim's and
collectively, we may have gotten that System state backed up to CD.
Apparently I needed a new driver. I used Jim' directions on how to get one.

After installing my newly-downloaded driver, I transferred a *.txt file and
an *.exe file to a CD on my E: read-write drive. They both transferred just
fine. So I tried backing up an *.exe file and transferring that *.bkf to
CD....the method you suggested. Seemed to work just fine.
So, while my luck was running good for a change, I backed up the System
State and transferred that file to CD. Worked perfectly. Almost too
perfectly. Only took 4-5 seconds to transfer a 242MB System State file to
CD. But my computer is only an 800mH machine and I think it should have taken
longer. However, reading the CD *.bkf file name properties, it shows exactly
the same file size as the original that I transferred over.

Is there any way I can test that CD System state file? [Without crashing my
system and restoring the System state "for real".]

Mark I think that this may be the success we three have sought. My thanks
to you for your advice and suggestions....and for sticking with it 'til the
problem was solved.

-Bill Martin Denver, CO

In microsoft.public.win2000.registry =?Utf-8?B?YmlsbG1hcnRpbjQ0?=
wrote:

Mark, many thanks for your advice.
I did as you said and everything seemed to be according to plan.
The file I had created on my hard drive was apparently written to
the CD. The screen showing the time remaining finally got down to
5 seconds....and stayed there for 10 minutes.
I concluded that something had gone wrong, so I used the dialog
box option to end the process.
But then I couldn't retreive the rewritable CD in E drive because
the screen said the copy process had been unable to finish and
unable to lock the file. I eventually used Ctl-Alt-Del and

I think you have some issues with your CD-RW or drivers or burning
software or discs ....

If you kill the writing-to-a-CD process you *will* be left with junk.
The write must complete without fatal errors. Also as you observed
Windows might hang and not want to shut down. In that event, waiting
a looong time may eventually allow Windows to shut down. YMMV

retrieved the CD. Then I tried to open the CD in MS Word2000 so I
could compare it to the file on the hard drive. But the screen

Well, I'm sorry, but opening binary files in Word is not an option.
Wrong tool. Hazardous to data. Et Cetera.

Most Windows versions contain the FC.EXE program (a command line
program) for comparing files byte for byte. From a CMD prompt try
FC /?

display was only little squares and pieces of words, so I couldn't
read it.

I suspect I did not create a valid backup.

The foremost advice is to enable "Verify" after backup inside
ntbackup. Always. Once a valid .bkf file exists on hard disk all
the other issues most likely are CD related. For one thing try a
brand new quality CD-R disk for a test burn.

Maybe Windows2000
Professional simply won't be tricked into backing up to a
rewritable CD.

Mark, thak you again for the advice. We almost made it.

I am reasonably certain that the backup-to-HD, then copy/burn to CD-R
or CD-RW should work. Done it thousands of times <G>. I think you
need to look for CD hardware and software problems. Disable A-V
real-time monitors during UDF copying perhaps.

I've never tried your original (or Jim's) methods to "burn direct
from ntbackup" though. I would not trust it myself and it would be
*slower* during the actual backup if it did work reliably.

Staying on-topic (registry) are you getting Event Log error messages
relating to the CD? Otherwise, one of the hardware groups may best
serve you for resolving CD/DVD/Windows issues.


[ snipped most prior ]

 

[Jim Byrd]

Hi Bill - YW, of course. First, about your ASPI download. No, it's just
for your ASPI devices, your CD-RW in your case. The reason there are so
many files is that it contains different versions of the 3 necessary files
for different OS's. Just run aspichk.exe and it will tell you if
you're OK now. If not, then read the Readme.txt carefully and follow the
directions there in Section VI. However, I think from what you've said that
you're probably all right now.

Next, there is a later firmware version for your drive, v.1.05. (The fact
that LiveUpdate didn't have it listed just means that they don't happen to
have data for that model.) Google is your friend, however.
http://www.google.com/search?sourceid=navclient&ie=UTF-8&q=NEC+NR-7700A
For example, you can download one here
http://www.opendrivers.com/driver/214403/NEC-NR-7700A-CD+RW-Firmware.html,
although I'm pretty sure from the Readme data in the file that it's ONLY for
the Retail version (and I'm not sure if even then this one would work in
Win2k), so you will need to contact your OEM provider and see if they offer
an update. Since you're working OK, you might just want to let it go unless
other problems develop (or you just can't stand not having the latest and
greatest ) REMEMBER - DON'T USE THIS ONE UNLESS YOUR DRIVE IS THE
RETAIL VERSION AND IT'S CLEAR THAT IT WORKS IN WIN2K. You always need to be
VERY CAREFULL about firmware updates. You didn't state your OEM, and with
just a quick look, I wasn't able to locate that particular OEM model on the
NEC site, but you might want to take a more extensive look. I would suggest
your OEM supplier as the first choice, however.

Lastly, I appreciate the feedback. I can have a bit more confidence now in
recommending that approach to others in the future than I did after your
last post.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, your advice put me on the right track. I did as you said.
Downloaded a new driver.
A bit more below.

Hi Bill - Well, first YW, of course. However, I'm sorry that
approach didn't work for you, but I do appreciate the feedback. I
may have to try it myself just to check. The fact that you
had errors when writing would imply to me that you either have
issues with your CD Drive (do you have such write errors using a
normal CD write program such as Easy CD Creator or Nero?)

After installing my newly-downloaded driver, I transferred a *.txt
file and an *.exe file to a CD on my E: read-write drive. They both
transferred just fine. So I tried backing up an *.exe file and
transferring that *.bkf to CD. Seemed to work just fine.
So, while my luck was running good for a change, I backed up the
System State and transferred that file to CD. Worked perfectly.
Almost too perfectly. Only took 4-5 seconds to transfer a 242MB
System State file to CD. But my computer is an 800mH machine and I
think it should have taken longer. However, reading the CD *.bkf file
name properties, it shows exactly the same file size as the original
that I transferred over.
Is there any way I can test that CD System state file?

or possibly a system incompatibility in your ASPI drivers.

Jim, do I have more than one ASPI driver? I only downloaded one Zip
file from the ASPI web site. It has two folders and 18 files in it
when unzipped. Is it likely that some of those are for my read-only
and floppy drive as well as my read-write drive?

You can get ASPIChk and the latest drivers (4.71 I think?) here:
http://www.adaptec.com/worldwide/su...sess=no&language=English+US&prodkey=ASPI-4.70

IIRC, Nero also provides updated ASPI drivers.

You might also want to check whether you have the most current
firmware for your CD RW drive. You can download LiveUpdate from
this site to check that: http://www.drvupdate.com/ Direct download
here: http://www.drvupdate.com/liveupdate/setup/LiveUpdateSetup.exe

My firmware for the read-write CD drive came from my Computer OEM
Back-Up CD. When I ran LiveUpdate, a message box said "There's no
device supported by Live Update on your system".
My read-write drive is a NEC NR-7700A. The ASPI driver I downloaded
seemed to work OK.
Shouldn't I be able to update my firmware as well? My firmware
version is
1.01 which sounds like an original version.

"The LiveUpdate Program is a smart tool that enables you to upgrade
your drive's firmware automatically. Through this powerful tool,
your drive will always be optimized for performance and
compatibility with the lastest media."

I've never had a problem with it, but again, use AT YOUR OWN RISK
(since it concerns firmware). Read and follow the User's Guide
carefully.


Or you may just want to forget the whole thing.

I'll admit, I DID get pretty discouraged....but thanks to your
generous assistance, Jim, I seem to have gotten that System State
file over to CD. Many thanks for hanging in there with me.

- Bill Martin Denver, CO

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, Thank you for your help and advice. Your instructions were
quite good and every step seemed to proceed as expected.

When I got to the last step - actually writing onto the renamed
rewritable CD drive, that writing began perfectly. Then it paused
because it was unable to copy one file onto the CD. I clicked OK and
it resumed, only to stop at another file it had some sort of trouble
with.
I decided the Backup CD was probably incorrect by now and never
going to be able to restore my System State, should I ever need to.
So the next time it stopped and the screen gave me an option to
quit, I did so.
Then the rewritable E: drive became inoperable so I used Ctl-Alt-Del
to get out - and it wouldn't close the drive. Repeated trys failed
to close the E: drive so I finally shut off the computer.
Took forever to shut down, so something was really messed up.
Maybe the new Network Place for the renamed E drive had something to
do with it. I guess we'll never know.

Apparently Windows2000 Professional is just not going to copy my
System State data to a rewritable drive, no matter what trick I try.

Jim, thanks again for a good try.

-Bill Martin Denver, CO



:

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try the
following approach AT YOUR OWN RISK courtesy of Mr. Petrus in a
posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user
way back in Aug of 2001. I haven't tried this, so I can't verify
whether it works or not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it
does not, add manually by choosing [Add a new device]. Select [No,
I want to select hardware from a list]. Select hardware type as
Network adapters. Choose Microsoft as the manufacturer and
'Microsoft Loopback Adapter' as the device.

Once installed, right click the CDRW, select properties, then
sharing, and enter a name for the device without any spaces in it.
You may need to use your CDRW software (e.g., Adaptec DirectCD,
etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the
CDRW as the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the
bottom of the window that asks you to define the 'Backup media or
file name': Do not select your CDRW but choose the network device
you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In billmartin44 <[email protected]> typed:
I am registered as Administrator for my stand-alone computer,
using Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk,
so I'm using a rewritable CD in drive E. I changed the drive
letter from A: to E: .
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not
the System State.
What should I do to allow the System State backup?

 

[Mark V]

In microsoft.public.win2000.registry =?Utf-8?B?YmlsbG1hcnRpbjQ0?=
wrote:

Mark, I used several pieces of your advice as well as several of
Jim's and collectively, we may have gotten that System state
backed up to CD. Apparently I needed a new driver. I used Jim'
directions on how to get one.

After installing my newly-downloaded driver, I transferred a *.txt
file and an *.exe file to a CD on my E: read-write drive. They
both transferred just fine. So I tried backing up an *.exe file
and transferring that *.bkf to CD....the method you suggested.
Seemed to work just fine. So, while my luck was running good for a
change, I backed up the System State and transferred that file to
CD. Worked perfectly. Almost too perfectly. Only took 4-5
seconds to transfer a 242MB System State file to CD. But my
computer is only an 800mH machine and I think it should have taken
longer. However, reading the CD *.bkf file name properties, it
shows exactly the same file size as the original that I
transferred over.

Is there any way I can test that CD System state file? [Without
crashing my system and restoring the System state "for real".]

Keeping it simple.
* Enable "Verify" for the job inside ntbackup. That will read from
the completed BKF file comparing it to sources.
* Use FC.EXE to compare the BKF file on disk (HD) with the one on
disc (CD). See FC /? you may need (probably) the "/b" switch.

You can also have ntbackup load the BKF file as the first step in a
Restore operation. Quite likely if there was any BKF file
corruption, ntbackup would see it immediately upon loading the file.

[ ]

 

[Jim Byrd]

Hi Bill - I just ran across this - I'm NOT recommending it, since I don't
know anything about its effectiveness/safety, and it costs (~$30?) and I
don't normally recommend other than free, but thought you might want to
investigate it for your particular problem. It sounds pretty good, if it
works as advertised. http://www.firestreamer.com/

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, your advice put me on the right track. I did as you said.
Downloaded a new driver.
A bit more below.

Hi Bill - Well, first YW, of course. However, I'm sorry that
approach didn't work for you, but I do appreciate the feedback. I
may have to try it myself just to check. The fact that you
had errors when writing would imply to me that you either have
issues with your CD Drive (do you have such write errors using a
normal CD write program such as Easy CD Creator or Nero?)

After installing my newly-downloaded driver, I transferred a *.txt
file and an *.exe file to a CD on my E: read-write drive. They both
transferred just fine. So I tried backing up an *.exe file and
transferring that *.bkf to CD. Seemed to work just fine.
So, while my luck was running good for a change, I backed up the
System State and transferred that file to CD. Worked perfectly.
Almost too perfectly. Only took 4-5 seconds to transfer a 242MB
System State file to CD. But my computer is an 800mH machine and I
think it should have taken longer. However, reading the CD *.bkf file
name properties, it shows exactly the same file size as the original
that I transferred over.
Is there any way I can test that CD System state file?

or possibly a system incompatibility in your ASPI drivers.

Jim, do I have more than one ASPI driver? I only downloaded one Zip
file from the ASPI web site. It has two folders and 18 files in it
when unzipped. Is it likely that some of those are for my read-only
and floppy drive as well as my read-write drive?

You can get ASPIChk and the latest drivers (4.71 I think?) here:
http://www.adaptec.com/worldwide/su...sess=no&language=English+US&prodkey=ASPI-4.70

IIRC, Nero also provides updated ASPI drivers.

You might also want to check whether you have the most current
firmware for your CD RW drive. You can download LiveUpdate from
this site to check that: http://www.drvupdate.com/ Direct download
here: http://www.drvupdate.com/liveupdate/setup/LiveUpdateSetup.exe

My firmware for the read-write CD drive came from my Computer OEM
Back-Up CD. When I ran LiveUpdate, a message box said "There's no
device supported by Live Update on your system".
My read-write drive is a NEC NR-7700A. The ASPI driver I downloaded
seemed to work OK.
Shouldn't I be able to update my firmware as well? My firmware
version is
1.01 which sounds like an original version.

"The LiveUpdate Program is a smart tool that enables you to upgrade
your drive's firmware automatically. Through this powerful tool,
your drive will always be optimized for performance and
compatibility with the lastest media."

I've never had a problem with it, but again, use AT YOUR OWN RISK
(since it concerns firmware). Read and follow the User's Guide
carefully.


Or you may just want to forget the whole thing.

I'll admit, I DID get pretty discouraged....but thanks to your
generous assistance, Jim, I seem to have gotten that System State
file over to CD. Many thanks for hanging in there with me.

- Bill Martin Denver, CO

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

Jim, Thank you for your help and advice. Your instructions were
quite good and every step seemed to proceed as expected.

When I got to the last step - actually writing onto the renamed
rewritable CD drive, that writing began perfectly. Then it paused
because it was unable to copy one file onto the CD. I clicked OK and
it resumed, only to stop at another file it had some sort of trouble
with.
I decided the Backup CD was probably incorrect by now and never
going to be able to restore my System State, should I ever need to.
So the next time it stopped and the screen gave me an option to
quit, I did so.
Then the rewritable E: drive became inoperable so I used Ctl-Alt-Del
to get out - and it wouldn't close the drive. Repeated trys failed
to close the E: drive so I finally shut off the computer.
Took forever to shut down, so something was really messed up.
Maybe the new Network Place for the renamed E drive had something to
do with it. I guess we'll never know.

Apparently Windows2000 Professional is just not going to copy my
System State data to a rewritable drive, no matter what trick I try.

Jim, thanks again for a good try.

-Bill Martin Denver, CO



:

Hi Bill - Backup doesn't work directly with CD-RW. You can backup
to disk and then copy it over as Mark suggested, or you can try the
following approach AT YOUR OWN RISK courtesy of Mr. Petrus in a
posting in
microsoft.public.win2000.general,microsoft.public.win2000.new_user
way back in Aug of 2001. I haven't tried this, so I can't verify
whether it works or not:


Here is the trick for CDRW backups in Windows 2000:

Go to [Add hardware]. Choose [Add/Troubleshoot a Device]. When it
does not, add manually by choosing [Add a new device]. Select [No,
I want to select hardware from a list]. Select hardware type as
Network adapters. Choose Microsoft as the manufacturer and
'Microsoft Loopback Adapter' as the device.

Once installed, right click the CDRW, select properties, then
sharing, and enter a name for the device without any spaces in it.
You may need to use your CDRW software (e.g., Adaptec DirectCD,
etc.) to accomplish this.

Then go to My Network Places and [Add Network Place] and define the
CDRW as the device using exactly this format:

\\mycomputername\nameofCDRWdrive

Now when you use MS Backup, on the Backup tab, in the box at the
bottom of the window that asks you to define the 'Backup media or
file name': Do not select your CDRW but choose the network device
you mapped by typing:

\\mycomputername\nameofCDRWdrive\backupfilename.bkf




--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In billmartin44 <[email protected]> typed:
I am registered as Administrator for my stand-alone computer,
using Windows 2000 Professional.
I regularly use Drive E: to backup data files on a rewritable CD.

I used Run>Programs>Accessories>Backup [to back up the System
State]. On the Backup dialog screen:
- Clicked on the Backup tab.
- Placed a checkmark in System State
- The Backup media box showed A:\ but I want it all on one disk,
so I'm using a rewritable CD in drive E. I changed the drive
letter from A: to E: .
- Clicked on: Start Backup
An error message appears: E: is not a valid drive or you do not
have access

I changed the Backup media drive back to A: and wrote one Floppy
disk, just to verify that my Adminiatrator permission was OK.
So, there's some reason why I can back up other files on drive E:
but not
the System State.
What should I do to allow the System State backup?