This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Error'Insert disk 1'
Started by
BrightIdeal
, Dec 16 2003 15:10
14 replies to this topic
Posted 16 December 2003 - 15:10
The situation is below,
1.I have installed a product from network.
2.I try to upgrade it with reinstall=veums and reinstall = all.
3.I upgrade it by running setup from CD image.
4.during reinstall,it prompt a message box 'please insert disk 1'
I wonder how can I deal with this error.
Thanks a lot!!
1.I have installed a product from network.
2.I try to upgrade it with reinstall=veums and reinstall = all.
3.I upgrade it by running setup from CD image.
4.during reinstall,it prompt a message box 'please insert disk 1'
I wonder how can I deal with this error.
Thanks a lot!!
Posted 16 December 2003 - 17:32
It seems your install can't find some or all of it's source files.
Are your files or cabs on the cd (in the same structure as they existed on the network)?
Check the media table for information on where the install expects the files to be. You'll also find your 'please insert disk 1' message in there (as well as under the "HKCR\Installer\Products\<GUID>\SourceList\Media" registry key).
By the way, your public properties should be uppercase, and the first one should be called "REINSTALLMODE".
Are your files or cabs on the cd (in the same structure as they existed on the network)?
Check the media table for information on where the install expects the files to be. You'll also find your 'please insert disk 1' message in there (as well as under the "HKCR\Installer\Products\<GUID>\SourceList\Media" registry key).
By the way, your public properties should be uppercase, and the first one should be called "REINSTALLMODE".
Posted 16 December 2003 - 17:51
Sorry... I forgot to this extract from the SDK relating to the "Media table":
"The label attributed to the volume. This is the volume label returned by the GetVolumeInformation function. If the SourceDir property refers to a removable (floppy or CD-ROM) volume, then this volume label is used to verify that the proper disk is in the drive before attempting to install files. The entry in this column must match the volume label of the physical media."
Scott.
"The label attributed to the volume. This is the volume label returned by the GetVolumeInformation function. If the SourceDir property refers to a removable (floppy or CD-ROM) volume, then this volume label is used to verify that the proper disk is in the drive before attempting to install files. The entry in this column must match the volume label of the physical media."
Scott.
Posted 16 December 2003 - 18:04
The structure is same.
So what can I do to reinstall with the CD ,if user have installed the previous version from network or map driver??
Thank you very much for your help.
So what can I do to reinstall with the CD ,if user have installed the previous version from network or map driver??
Thank you very much for your help.
Posted 16 December 2003 - 18:42
Some more information might be useful in determining the problem...
1) Are the files compressed inside ".cab" files?
2) Which version of the Windows Installer are you using?
3) Where is the MSI file relative to the root of the CD?
4) What's under "HKCR\Installer\Products\<GUID>\SourceList\".
5) What entries are in your media table?
6) A log file might provide some extra insight?
Thanks.
1) Are the files compressed inside ".cab" files?
2) Which version of the Windows Installer are you using?
3) Where is the MSI file relative to the root of the CD?
4) What's under "HKCR\Installer\Products\<GUID>\SourceList\".
5) What entries are in your media table?
6) A log file might provide some extra insight?
Thanks.
Posted 16 December 2003 - 18:59
While I'm waiting for your replies, you could try adding the following property to your command line (only if your MSI file isn't in the Root of your CD):
MEDIAPACKAGEPATH="\MSIFolderName\"
MEDIAPACKAGEPATH="\MSIFolderName\"
Posted 16 December 2003 - 19:18
1.Not all the files compressed inside the .cab files.There are some external files.
2.The version of installer is 2.0.2600
3.The msi file in the subfolder of the root of CD,but installer try to find this from the root of CD.
4.Media--Key 1,2,3,4--value Disk1:1
Net --Key 1 value : the net disk driver
5.No any entries in the Midia Table.I do not know how to set the table.
6.When installfiles run ,the msg prompt.
Thanks a lot.
2.The version of installer is 2.0.2600
3.The msi file in the subfolder of the root of CD,but installer try to find this from the root of CD.
4.Media--Key 1,2,3,4--value Disk1:1
Net --Key 1 value : the net disk driver
5.No any entries in the Midia Table.I do not know how to set the table.
6.When installfiles run ,the msg prompt.
Thanks a lot.
Posted 17 December 2003 - 15:00
yes ,I have tried this.but it doesnot work.
do you think this is a problem we can solved from setup program?
Is it limited by installer??
do you think this is a problem we can solved from setup program?
Is it limited by installer??
Posted 17 December 2003 - 15:21
How can you have no entries in your Media table? Do you have entries in your File table?
Did your original package have Media table entries?
Did your original package have Media table entries?
Posted 17 December 2003 - 15:31
No.There are no any entries in the Midia Table neither the original package and the current package:(
Posted 17 December 2003 - 16:51
If your package has "File" table entries, and no media table entries, then I'm stumped!!
As far as I can make out from the SDK, and from personal experience, the "Sequence" column of the "File" table refers to the "Media" table to determine the location of the files.
I've had similar problems to yours which have been fairly easy to resolve (but I always had "Media" table entries. I can even recreate your error message by installing an MSI from a subfolder on a floppy disk.
Sorry I can't offer any more advice! Maybe someone else knows how it's possible for a package containing files to work without any entries in the "Media" table?
As far as I can make out from the SDK, and from personal experience, the "Sequence" column of the "File" table refers to the "Media" table to determine the location of the files.
I've had similar problems to yours which have been fairly easy to resolve (but I always had "Media" table entries. I can even recreate your error message by installing an MSI from a subfolder on a floppy disk.
Sorry I can't offer any more advice! Maybe someone else knows how it's possible for a package containing files to work without any entries in the "Media" table?
Posted 18 December 2003 - 07:46
Hi Scotsmanscott,
I add entry Mediapackage entry in the registry ket media.
And the installation works fine.
Thank you very much for you help.
I add entry Mediapackage entry in the registry ket media.
And the installation works fine.
Thank you very much for you help.
Posted 18 December 2003 - 10:53
Hi,
I'm glad you found a solution that suits you!
But this means you have to edit the registry for every PC that you wish to upgrade!
If I use the MEDIAPACKAGEPATH property on first installation, the following REG_SZ key is written to the registry:
"HKCR\Installer\Products\COMPRESSEDGUID\Sourcelist\Media\MediaPackage"
The same key is automatically written (without explicit use of the MEDIAPACKAGEPATH property) if the source MSI was contained within a subfolder on a removable disk.
However, using the MEDIAPACKAGEPATH property during a major upgrade by REINSTALL (from a different source path), does not seem to rewrite this key. I find this strange!
I'm glad you found a solution that suits you!
But this means you have to edit the registry for every PC that you wish to upgrade!
If I use the MEDIAPACKAGEPATH property on first installation, the following REG_SZ key is written to the registry:
"HKCR\Installer\Products\COMPRESSEDGUID\Sourcelist\Media\MediaPackage"
The same key is automatically written (without explicit use of the MEDIAPACKAGEPATH property) if the source MSI was contained within a subfolder on a removable disk.
However, using the MEDIAPACKAGEPATH property during a major upgrade by REINSTALL (from a different source path), does not seem to rewrite this key. I find this strange!