XxEDGExX Posted March 27, 2005 Posted March 27, 2005 Right, I have spent 6 hours, trying desperately to produce a windows CD with the rather nice lookin nlite proggy. I was using the latest version; nlite0998bi.I have collected all the info needed, fresh copy if XP files to manipulate from disk. All runs fine UNTIL the VERY last step, when nlite atempts to finalise files.I get the following error msg:Microsoft Cabinet Maker has encountered a problem and needs to close.AppName: makecab.exe AppVer: 5.1.2600.2180 ModName: makecab.exeModVer: 5.1.2600.2180 Offset: 00004038I have tried everything humanly possible, even Installing an original version of XP SP2 ! It would still fail. I can believe I am the first one experienceing this problem, but I could not find anything related in this Forum. Has anyone got a clue whats going on ? I apreciate any help/hintsMike
XxEDGExX Posted March 27, 2005 Author Posted March 27, 2005 Comon lads !I dont believe that I am the very first one experiencing problems with the MS Cabinet Maker...
nuhi Posted March 31, 2005 Posted March 31, 2005 Get some other makecab.exe and put it into nlite\data
Acheron Posted March 31, 2005 Posted March 31, 2005 Feature request: Makecab verification. In case makecab is wrong version nLite should warn the user
anfo1369 Posted July 20, 2005 Posted July 20, 2005 (edited) I, too, am having this problem. I'm using:1. nLite v1.0 beta 52. Windows XP Pro (VLK) with SP2 integratedo.k., i replaced makecab into nlite\data like suggested.Still having the same problem with makecab.exe crashing during Finalizing...just making iso = no problems.remove components + make iso = makecab crashintegrating drivers + remove components + make iso = makecab crashintegrate drivers + remove components + UA Setup + make iso = makecab crashin short, anything addition to make bootable iso = makecab crashQuestion: What is the makecab.exe for?Question: If I cannot Remove Components, then what is the point of nLite? -- sorry if question #2 seems rude, i'm exasparated at trying this. So many others seem to be able to use this w/o error; and, I would like to as well.==Edit again==After Checking Event Viewer, I find thisFaulting application makecab.exe, version 5.1.2600.2180,faulting modulemakecab.exe,version 5.1.2600.2180, fault address 0x00013d45.Also these fault addresses: => 0x00013bbb => 0x00013ad3==Edit...yes, again ==OK, dug out my clean/gold xp (ie. no SP) .. same problems as above with makecab.exe from the original xp disc, not SP2's version. Edited July 20, 2005 by anfo1369
Electrician Posted July 21, 2005 Posted July 21, 2005 Although I use nlite to process files for a win2k build, I am running it on anXPsp2 system. Have not had any problems with makecab.exeThe version in my sys32 and ddlcache are 5.1.2600.2180 Size 84KB.So I don't think it is TRULY a problem with makecab, since you guys verified the file by copying.Have you tried running makecab on any file from a cmd prompt?
nuhi Posted July 21, 2005 Posted July 21, 2005 anfo1369, Expand this file and take makecab from there, it's legalhttp://download.microsoft.com/download/pla...n-us/cabsdk.exePut it into your system32 folder by overwriting old one.Also be sure there is no makecab.exe in nlite\data folder.And if this helps then compress and attach example of not working makecab so I may detect it.Thanks
anfo1369 Posted July 24, 2005 Posted July 24, 2005 Thanks,nuhi.My RAM seems to have gone bad, i've run diagnostics and it failed.This may have alot to do with my error..I had to swap out my mainboard for a SDRAM one; however,this one powered up 3 times and died on me.Currently having to run my other systemMainboard: Asus P2B-FCPU: Pentium II 350@466RAM: 2x 128MB PC133 SDRAMOS: Windows 2000 Professional I guess I won't be running nLite for awhile - It will be months(hopefully Christmas) before the P4 will be back up and running.
glent Posted July 24, 2005 Posted July 24, 2005 I see you have overclocked your CPU, could you set it back to 350Mhz, run nlite again post your result?
anfo1369 Posted July 25, 2005 Posted July 25, 2005 I see you have overclocked your CPU, could you set it back to 350Mhz, run nlite again post your result?<{POST_SNAPBACK}>I guess I won't be running nLite for awhile - It will be months(hopefully Christmas) before the P4 will be back up and running.I'm not even about to attempt it on here.
dirtwarrior Posted July 25, 2005 Posted July 25, 2005 (edited) Is there a program to do make cab with a nice GUI front end like winrar or similar?found ithttp://www.msfn.org/board/index.php?showtopic=25442&hl= Edited July 25, 2005 by dirtwarrior
rentz Posted July 26, 2005 Posted July 26, 2005 (edited) anfo1369, Expand this file and take makecab from there, it's legalhttp://download.microsoft.com/download/pla...n-us/cabsdk.exePut it into your system32 folder by overwriting old one.Also be sure there is no makecab.exe in nlite\data folder.And if this helps then compress and attach example of not working makecab so I may detect it.ThanksI have the same problem with 1.0beta5 when integrating drivers, tried the above but still got the "...needs to close..."-scenario.I previosly ran 0.99.9 without problems.I run WinXP SP2 (5.1.2600)*EDIT* Just rolled back to 0.99.9 and i see the same problems.I get back to you when I have more info, something must have changed. Edited July 27, 2005 by rentz
rentz Posted July 28, 2005 Posted July 28, 2005 I get back to you when I have more info, something must have changed.<{POST_SNAPBACK}>Alright, I've pinpointed the problem to this file: DISKKU.VER(file is part of a driver I downloaded from IBM, renamed here so i could attach it).If I remove that file and then run Driver Integration everything work just fine, I don't get an error.Maybe someone older and wiser than me figure out why.DISKKU.TXT
nuhi Posted July 28, 2005 Posted July 28, 2005 (edited) rentz, I had similiar errors with some CAT files.Makecab is weird...gonna replace it with some dll in one of the next versions.Until then just delete that file before integration.edit: ok, fixed in next version, still with makecab Edited July 28, 2005 by nuhi
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now