Unable to read a CD

  • Thread starter Thread starter Jason Krause
  • Start date Start date
J

Jason Krause

Hello all,

Here is what I did:
1. Installed Windows XP on the target machine.
2. Ran TAP.exe
3. Imported the .pqm file into the Component Designer.
4. Selected a "Windows-based Terminal Professional" Prototype for that
component (maybe this is where the mistake is?)
5. I then import the saved component into the "Component Database Manager".
6. I go into the "Target Designer" and add my new component.
7. I add the following components:
NTFS
NT Loader
NTFS Format
Language Support
User Interface Core
8. I then choose to "Check Dependencies"
9. Then I choose "Build Target Image"
10. Put the image on a new HD and boot everything up.

It goes through the Boot Agent process okay, and I even have the desktop
and start menu, etc., but when I try to read a CD I get this error:
"Windows cannot read from this disk. The disk might be corrupted, or it
could be using a format that is not compatible with Windows." I have
verified that it is not the CD. Am I missing a component when setting
up the "Target Designer"?

On an unrelated note, do I have to add a specific component in order to
change my Display settings?

Thanks,
Jason
 
Jason said:
Hello all,

Here is what I did:
1. Installed Windows XP on the target machine.
2. Ran TAP.exe
3. Imported the .pqm file into the Component Designer.
4. Selected a "Windows-based Terminal Professional" Prototype for that
component (maybe this is where the mistake is?)
5. I then import the saved component into the "Component Database
Manager".
6. I go into the "Target Designer" and add my new component.
7. I add the following components:
NTFS
NT Loader
NTFS Format
Language Support
User Interface Core
8. I then choose to "Check Dependencies"
9. Then I choose "Build Target Image"
10. Put the image on a new HD and boot everything up.

It goes through the Boot Agent process okay, and I even have the desktop
and start menu, etc., but when I try to read a CD I get this error:
"Windows cannot read from this disk. The disk might be corrupted, or it
could be using a format that is not compatible with Windows." I have
verified that it is not the CD. Am I missing a component when setting
up the "Target Designer"?
CDFS.

On an unrelated note, do I have to add a specific component in order to
change my Display settings?
Click to expand...
You should be able to set them in the target designer, but to change
them in the image you'll need whichever component contains desk.cpl
 
Thanks for the quick response Adora.

I added the CDFS component to the "Target Designer". I'll let you know
how it goes. By the way, is there a good resource online that can help
determine which components are needed for specific windows functionality?
You should be able to set them in the target designer, but to change
them in the image you'll need whichever component contains desk.cpl
Click to expand...

How does one determine which component contains desk.cpl? I was able to
find the "Display Control Panel" component under:
Software -> System -> User Interface -> Shells -> Windows Shell

But that component was already added to my image. I'll try this new
build and go from there.

Thanks,
Jason
 
Jason said:
How does one determine which component contains desk.cpl? I was able
to find the "Display Control Panel" component under:
Software -> System -> User Interface -> Shells -> Windows Shell
Click to expand...

You can create filters in Target Designer to filter for components
containing specific files.
 
Jason,

Before I explain the filter manager stuff, we need to talk about
component visibility. Each component has a visibility level between
100 and 10000. The default visibility used by Target Designer is 1000.
This means that, when first installed you can't see any components
with a visibility less than 1000. Most components with visibility <
1000 are normally referenced by higher visibility components, and end
up being included automatically. However, if you are trying to build a
low-footprint image, sometimes you need to manually include certain
components only. I keep my visibility set at 100 all the time, which
makes Target Designer somewhat slower, and makes my .SLX file look a
lot more complicated (many more components appear in the center window
of Target Designer).

To set the visibility, select 'Tools', 'Options', 'Advanced', and enter
100 in the "minimum visibility" box. If you do not do this you won't
see the component, ever.

Now that that is taken care of, here is how to search for a given
component:

In the upper left corner of Target Designer you will find a box that
says 'Filter'.
Click the button that looks like a funnel to the right of this box.
Click "New"
Fill in the name as 'Component Contains File'
In the "Filter Rules" box, double click on
"Component Contains the following File[filelist]",
In the bottom box double-click on the
[Double Click here], then enter the file name.
Click OK.
Click Apply Filter.

After a minute or two, the component window will show the component of
interest.
(Which happens to be
"Software::System Services::Base::Class Install Library - Desk")

To return to the normal component display, click in the "Filter" box,
and select
"All Components"

It is easy to modify this filter at any time, and it is very handy to
find components. Also, check out the other available filters

Also, have a look at KM's "Dependency Explorer" component from XPeTools
packages (www.xpefiles.com)

SteveS
stevesATeyeDASHimagingDOTcom
 
Looks like visibility was the problem. Thanks for your help Steves.



Jason,

Before I explain the filter manager stuff, we need to talk about
component visibility. Each component has a visibility level between
100 and 10000. The default visibility used by Target Designer is 1000.
This means that, when first installed you can't see any components
with a visibility less than 1000. Most components with visibility <
1000 are normally referenced by higher visibility components, and end
up being included automatically. However, if you are trying to build a
low-footprint image, sometimes you need to manually include certain
components only. I keep my visibility set at 100 all the time, which
makes Target Designer somewhat slower, and makes my .SLX file look a
lot more complicated (many more components appear in the center window
of Target Designer).

To set the visibility, select 'Tools', 'Options', 'Advanced', and enter
100 in the "minimum visibility" box. If you do not do this you won't
see the component, ever.

Now that that is taken care of, here is how to search for a given
component:

In the upper left corner of Target Designer you will find a box that
says 'Filter'.
Click the button that looks like a funnel to the right of this box.
Click "New"
Fill in the name as 'Component Contains File'
In the "Filter Rules" box, double click on
"Component Contains the following File[filelist]",
In the bottom box double-click on the
[Double Click here], then enter the file name.
Click OK.
Click Apply Filter.

After a minute or two, the component window will show the component of
interest.
(Which happens to be
"Software::System Services::Base::Class Install Library - Desk")

To return to the normal component display, click in the "Filter" box,
and select
"All Components"

It is easy to modify this filter at any time, and it is very handy to
find components. Also, check out the other available filters

Also, have a look at KM's "Dependency Explorer" component from XPeTools
packages (www.xpefiles.com)

SteveS
stevesATeyeDASHimagingDOTcom
Click to expand...
 
I just wanted to say thank you for this post. I am working on a dual boot
system and have a philips DVD8701 - it worked in XP but not on the dual boot
XPE. I search long and far to find the problem.

In XPE in device manager it would say it was running fine, however, I would
get the "Windows cannot read from this disk. The disk might be corrupted, or
it could be using a format that is not compatible with Windows." message. I
tried to find the driver for philips DVD8701 but did not have much luck.

Then I found the answer here that I need to add the CDFS component. It now
works in XP and XPE.
 
That's Great!

I have gotten so much help from this newsgroup, and I wanted to give
back a bit.
Good Luck

SteveS
StevesATeyeDASHimagingDOTcom
 
Back
Top