If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#31
|
|||
|
|||
Missing Cabs when Installing full file version of OneNote SP1 (and Office 2003 SP1)
Simon, there is no connection between the need for MSI and the request for
CAB files. The design of the Windows Installer is that binary patching requires that it verify against the installation source. The file hash can limit the need for the source, but unversioned files are still a problem. That's why the Local Install Source feature was created (which is controlled completely via SETUP.EXE - the Windows Installer knows nothing of LIS) so that the installation source files will always be available. There are some conditions in which all of the CABs will not be in the \MSOCache folder, and that is when users are seeing the 'cannot find xxxxxx.CAB' error. Simply inserting the CD will cause all of the missing CABs to be copied to the \MSOCache folder so that the CD should never be required again for patching. Sloan Crayton Microsoft "Simon Cooke" wrote in message ... On Mon, 2 Aug 2004 20:47:36 -0700, Chris_Pratley (MS) wrote: setup.exe sometimes has a little logic and other bits of code that are necessary for a setup to work correctly - not every setup.exe is just a plain MSI wrapper. But in this case, you just need to point the Sp1 patch setup at the MSI to get the setup to complete. BTW, With XP SP2 this requirement of Windows Installer is finally removed. Actually, Chris, not in this case... You do need to run the LISTool to remove the cached install files. I tried pointing the SP1 patch at the MSI file - it just kept asking for the CAB. |
#32
|
|||
|
|||
Missing Cabs when Installing full file version of OneNote SP1 (and Office 2003 SP1)
*sigh*
I went through this kind of crap once already with the TaxSaver team. They had a demo install on their website which tried to download its files from inside corpnet. We went around for a week of stupidity while I kept telling them to try using the installer from OUTSIDE the firewall. They kept insisting that it worked fine - because they kept trying to run it from WITHIN the firewall. I don't make these pronouncements lightly. I am not guessing. I'm telling you EXACTLY what I had to do to get it to work, and what did and did not work. Read my post again. On a Toshiba M200, default install of OneNote as shipped by the OEM, one HAS to run the LisTool to delete the installation source or the admin full install of SP1 will not work. Chris's suggestion that I point the installer at the MSI file when it asked for the CAB does NOT work. There is a problem with Office 2003 installs which are told to DELETE the installation source cache after they finish installation. It would appear that this operation does not correctly delete the cache, causing the admin full-file install to fault because it cannot find the files which its index is telling it should be in the install cache there. Inserting the CD does NOT do what you're talking about. The CD does NOT contain any CABs, and does not automatically install the CAB files into the MSOCache folder from the MSI. Running the LisTool tool to delete the install cache, however, causes the Admin full-file SP1 install to CORRECTLY and COMPLETELY install without any further error. On Tue, 3 Aug 2004 21:58:21 -0700, Sloan Crayton [MS] wrote: Simon, there is no connection between the need for MSI and the request for CAB files. The design of the Windows Installer is that binary patching requires that it verify against the installation source. The file hash can limit the need for the source, but unversioned files are still a problem. That's why the Local Install Source feature was created (which is controlled completely via SETUP.EXE - the Windows Installer knows nothing of LIS) so that the installation source files will always be available. There are some conditions in which all of the CABs will not be in the \MSOCache folder, and that is when users are seeing the 'cannot find xxxxxx.CAB' error. Simply inserting the CD will cause all of the missing CABs to be copied to the \MSOCache folder so that the CD should never be required again for patching. Sloan Crayton Microsoft "Simon Cooke" wrote in message ... On Mon, 2 Aug 2004 20:47:36 -0700, Chris_Pratley (MS) wrote: setup.exe sometimes has a little logic and other bits of code that are necessary for a setup to work correctly - not every setup.exe is just a plain MSI wrapper. But in this case, you just need to point the Sp1 patch setup at the MSI to get the setup to complete. BTW, With XP SP2 this requirement of Windows Installer is finally removed. Actually, Chris, not in this case... You do need to run the LISTool to remove the cached install files. I tried pointing the SP1 patch at the MSI file - it just kept asking for the CAB. |
#33
|
|||
|
|||
Missing Cabs when Installing full file version of OneNote SP1 (and Office 2003 SP1)
Can you elaborate on what you mean by the CD has no CABs?
Sloan Crayton Microsoft "Simon Cooke" wrote in message .. . *sigh* I went through this kind of crap once already with the TaxSaver team. They had a demo install on their website which tried to download its files from inside corpnet. We went around for a week of stupidity while I kept telling them to try using the installer from OUTSIDE the firewall. They kept insisting that it worked fine - because they kept trying to run it from WITHIN the firewall. I don't make these pronouncements lightly. I am not guessing. I'm telling you EXACTLY what I had to do to get it to work, and what did and did not work. Read my post again. On a Toshiba M200, default install of OneNote as shipped by the OEM, one HAS to run the LisTool to delete the installation source or the admin full install of SP1 will not work. Chris's suggestion that I point the installer at the MSI file when it asked for the CAB does NOT work. There is a problem with Office 2003 installs which are told to DELETE the installation source cache after they finish installation. It would appear that this operation does not correctly delete the cache, causing the admin full-file install to fault because it cannot find the files which its index is telling it should be in the install cache there. Inserting the CD does NOT do what you're talking about. The CD does NOT contain any CABs, and does not automatically install the CAB files into the MSOCache folder from the MSI. Running the LisTool tool to delete the install cache, however, causes the Admin full-file SP1 install to CORRECTLY and COMPLETELY install without any further error. On Tue, 3 Aug 2004 21:58:21 -0700, Sloan Crayton [MS] wrote: Simon, there is no connection between the need for MSI and the request for CAB files. The design of the Windows Installer is that binary patching requires that it verify against the installation source. The file hash can limit the need for the source, but unversioned files are still a problem. That's why the Local Install Source feature was created (which is controlled completely via SETUP.EXE - the Windows Installer knows nothing of LIS) so that the installation source files will always be available. There are some conditions in which all of the CABs will not be in the \MSOCache folder, and that is when users are seeing the 'cannot find xxxxxx.CAB' error. Simply inserting the CD will cause all of the missing CABs to be copied to the \MSOCache folder so that the CD should never be required again for patching. Sloan Crayton Microsoft "Simon Cooke" wrote in message ... On Mon, 2 Aug 2004 20:47:36 -0700, Chris_Pratley (MS) wrote: setup.exe sometimes has a little logic and other bits of code that are necessary for a setup to work correctly - not every setup.exe is just a plain MSI wrapper. But in this case, you just need to point the Sp1 patch setup at the MSI to get the setup to complete. BTW, With XP SP2 this requirement of Windows Installer is finally removed. Actually, Chris, not in this case... You do need to run the LISTool to remove the cached install files. I tried pointing the SP1 patch at the MSI file - it just kept asking for the CAB. |
#34
|
|||
|
|||
Missing Cabs when Installing full file version of OneNote SP1 (and
I'm having the same problem with installing an update to the OneNote that
came on Fujitsu Tablet. No preview version was installed or updates done prior to this attempt to upgrade to OneNote SP-1. Install looking for sku1a1.cab file. Have no source CD, and drive image that Fujitsu used for backup is not browsable. Fujitsu tech support suggested restoring drive image, thus wiping out hours of setup and installs. Perhaps there is some solution in the posts below, but discussion is way above my level. "Simon Cooke" wrote: Whenever I try to install OneNote 2003 SP1 or Office 2003 SP1 full-file service packs, I get "missing CAB file" errors. Does anyone know why this is happening? I have a Toshiba M205 PC, and as such don't have access to the CABs for OneNote, so I can't install the missing files from the install media as I don't have any. Needless to say, I really need the full file version to work. I get similar errors on the Office 2003 SP1 with missing CABs from FrontPage 2003. Thanks, Simon |
#35
|
|||
|
|||
no cabs
I had the same issue with my Averatec C3500 Tablet PC. It kept asking for a SKU1A1.CAB file. I followed Simon's suggestion and used the LISTool to remove the local installation source. Then the full SP1 patch install worked. OneNote came installed with the PC and I do not have a OneNote or Office 2003 install CD. All I have are some PC restore CDs which I expect would be similar to Simon's (I didn't even look on them), although I'm not an expert on this...
Last edited by klumpbk : February 10th, 2005 at 04:36 PM. Reason: correction |
Thread Tools | |
Display Modes | |
|
|