I am getting a strange error message when building and ISO using the new version of UBCD4WIN. I have created and burned ISO's in the past with previous versions with no errors. Looking at a previous topic I checked for the existenace of other copies of cygwin. There are none. I have deleted the directory and reinstalled several times as well as played with different plug in options. No success. The ISO is not created. Anyone have any clues or suggestions?
Here is the end of the log:
++++++
STEP 95: Build ISO
BCDW found
MkISOfs.exe version:
20 [main] ? 4812 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
D:\UBCD4Win\temp\mkisofs.exe (4812): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
MKISOFS-options:
-iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort D:\UBCD4Win\temp\pe_sort.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
22 [main] ? 4908 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
D:\UBCD4Win\temp\mkisofs.exe (4908): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
ISO succesfully created
; -----------------------------------------
; autobuild.cmd finished at
; Version: 2.0 beta4
; Date: Mon 02/18/2008
; Time: 16:22:27.92
; Extra debuging output can be found in D:\UBCD4Win\autobuild.log
Full Version: Error when building ISO
In a quick internet search I saw only two clear causes of this... a corrupted installed cygwin and duplicated cygwin dlls ... since the project does a hash check on its files, I'm going to guess that you missed another copy of cygwin somewhere... here is the webpage about going in that direction http://users.tkk.fi/~mlinjaah/cygwin_problem_make.html
QUOTE (rdsok @ Feb 18 2008, 05:21 PM) 
In a quick internet search I saw only two clear causes of this... a corrupted installed cygwin and duplicated cygwin dlls ... since the project does a hash check on its files, I'm going to guess that you missed another copy of cygwin somewhere... here is the webpage about going in that direction http://users.tkk.fi/~mlinjaah/cygwin_problem_make.html
Yes, I actually found that doc before I posted. I did a windows search and all it turned up was the product's version. I am going to try it on a different computer, just to rule out some strange compatibility with the Symantec products I have on the machine, and other stuff. That is the only stuff that was loaded since the last time I made a boot CD. I'll let you know what happens.
QUOTE (CanOpener @ Feb 18 2008, 07:34 PM)
QUOTE (rdsok @ Feb 18 2008, 05:21 PM)
In a quick internet search I saw only two clear causes of this... a corrupted installed cygwin and duplicated cygwin dlls ... since the project does a hash check on its files, I'm going to guess that you missed another copy of cygwin somewhere... here is the webpage about going in that direction http://users.tkk.fi/~mlinjaah/cygwin_problem_make.html
Yes, I actually found that doc before I posted. I did a windows search and all it turned up was the product's version. I am going to try it on a different computer, just to rule out some strange compatibility with the Symantec products I have on the machine, and other stuff. That is the only stuff that was loaded since the last time I made a boot CD. I'll let you know what happens.
Hi CanOpener,
I am having the same problem as yours, did you get the problem fixed? I don't have multiple cygwin -dll path problem, but I do have Symantec Endpoint Protection installed on my machine. Please let me know your solution. Thanks.
Hi CanOpener,
I am having the same problem as yours, did you get the problem fixed? I don't have multiple cygwin -dll path problem, but I do have Symantec Endpoint Protection installed on my machine. Please let me know your solution. Thanks.
[/quote]
No, I never got it fixed. I havn't had a chance to build it on another machine. I have been so busy I actually forgot about it. I am sure it is an endpoint issue. That program gives me more problems ....
Mike T.
I am having the same problem as yours, did you get the problem fixed? I don't have multiple cygwin -dll path problem, but I do have Symantec Endpoint Protection installed on my machine. Please let me know your solution. Thanks.
[/quote]
No, I never got it fixed. I havn't had a chance to build it on another machine. I have been so busy I actually forgot about it. I am sure it is an endpoint issue. That program gives me more problems ....
Mike T.
I had a similar problem and found an old cygwin1.dll file in my path. Eliminating it did not fix the problem. I ran the builder from within a 32-bit XP VM with access to same UBCD4Win fileset and it worked fine. It seems it's not compatible with 64-bit Windows or possibly something else on my system. It did work properly with v3.10 and older versions. For reference I included the error output.
Cheers,
-felipe
QUOTE
MkISOfs.exe version:
2 [main] ? 11016 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11016): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
MKISOFS-options:
-iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort I:\UBCD4Win_v312\temp\pe_sort.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
I:\UBCD4Win_v312\UBCD4VSS_312>"I:\UBCD4Win_v312\temp\mkisofs.exe" -iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort I:\UBCD4Win_v312\temp\pe_sort.txt -duplicates-once -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "I:\UBCD4Win_v312\UBCD4WinBuilder.iso" . 2>&1 | mtee /+ I:\UBCD4Win_v312\autobuild.log
2 [main] ? 11464 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11464): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start->Find/Search facility
te all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
ISO succesfully created
2 [main] ? 11016 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11016): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
MKISOFS-options:
-iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort I:\UBCD4Win_v312\temp\pe_sort.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
I:\UBCD4Win_v312\UBCD4VSS_312>"I:\UBCD4Win_v312\temp\mkisofs.exe" -iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort I:\UBCD4Win_v312\temp\pe_sort.txt -duplicates-once -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "I:\UBCD4Win_v312\UBCD4WinBuilder.iso" . 2>&1 | mtee /+ I:\UBCD4Win_v312\autobuild.log
2 [main] ? 11464 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11464): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start->Find/Search facility
te all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
ISO succesfully created
Cheers,
-felipe
QUOTE (felipegeek @ Mar 23 2008, 03:30 PM)
I had a similar problem and found an old cygwin1.dll file in my path.
It did work properly with v3.10 and older versions.
There is the same cygwin1.dll at v3.10 and v3.12. Most likely that's not the difference.It did work properly with v3.10 and older versions.
Did you changed other software in the meantime?
Did you used 64-bit Windows before?
QUOTE
I ran the builder from within a 32-bit XP VM with access to same UBCD4Win fileset and it worked fine.
Yes, a VM is a nice work arround.
QUOTE
MkISOfs.exe version:
2 [main] ? 11016 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11016): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Do a system wide search for the file "cygwin1.dll".2 [main] ? 11016 shared_info::initialize: size of shared memory region changed from 21008 to 19988
I:\UBCD4Win_v312\temp\mkisofs.exe (11016): *** user shared size version mismatch detected - 0xA65C/0xA660.
You have multiple copies of cygwin1.dll on your system.
Keep the most recent version. Overwrite older versions with the most recent version.
Copy the most recent version to <UBCD4Win>\plugin\AutoBuild\Files\
Reboot machine.
The only cgywin1.dll I have is in the UBCD4WIN directory (4 of them actually with two different file sizes). This is a new install of UBCD4WIN on another machine. here is a slightly different form of the error:
STEP 95: Build ISO
Check for different Bootloaders:
BCDW found
MkISOfs.exe version:
20 [main] ? 3084 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
C:\UBCD4Win\temp\mkisofs.exe (3084): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
MKISOFS-options:
-iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort C:\UBCD4Win\temp\pe_sort.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
C:\UBCD4Win\BartPE>"C:\UBCD4Win\temp\mkisofs.exe" -iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort C:\UBCD4Win\temp\pe_sort.txt -duplicates-once -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "C:\UBCD4Win\UBCD4WinBuilder.iso" . 2>&1 | mtee /+ C:\UBCD4Win\autobuild.log
20 [main] ? 3112 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
C:\UBCD4Win\temp\mkisofs.exe (3112): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
I think there is something going on as I never had this issue before. There are no other copies of that .dll. I have checked, several times (unless Windows search is lying. And yes, I have it checking system directories and hidden folders). I think it is interesting that another poster with this problem says he also has Symantec Endpoint Protection Installed. Both of my powerful machines have that program installed. I don't have one available at the moment that doesn't have that product installed. Anybody have any suggestions on where to look next? I don't quite understand what the program is trying to do when it craps out. The error looks like it cannot allocate enough memory (1.5 gb free). Are there any options on the plug-ins I can deselect to keep this feature from being activated?
STEP 95: Build ISO
Check for different Bootloaders:
BCDW found
MkISOfs.exe version:
20 [main] ? 3084 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
C:\UBCD4Win\temp\mkisofs.exe (3084): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
MKISOFS-options:
-iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort C:\UBCD4Win\temp\pe_sort.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
C:\UBCD4Win\BartPE>"C:\UBCD4Win\temp\mkisofs.exe" -iso-level 4 -volid ""UBCD4Windows"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort C:\UBCD4Win\temp\pe_sort.txt -duplicates-once -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "C:\UBCD4Win\UBCD4WinBuilder.iso" . 2>&1 | mtee /+ C:\UBCD4Win\autobuild.log
20 [main] ? 3112 init_cheap: Couldn't reserve 3600084 bytes of space for cygwin's heap, Win32 error 487
C:\UBCD4Win\temp\mkisofs.exe (3112): *** AllocationBase 0x61750000, BaseAddress 0x61790000, RegionSize 0x7000, State 0x1000
I think there is something going on as I never had this issue before. There are no other copies of that .dll. I have checked, several times (unless Windows search is lying. And yes, I have it checking system directories and hidden folders). I think it is interesting that another poster with this problem says he also has Symantec Endpoint Protection Installed. Both of my powerful machines have that program installed. I don't have one available at the moment that doesn't have that product installed. Anybody have any suggestions on where to look next? I don't quite understand what the program is trying to do when it craps out. The error looks like it cannot allocate enough memory (1.5 gb free). Are there any options on the plug-ins I can deselect to keep this feature from being activated?
QUOTE (CanOpener @ Mar 26 2008, 01:37 PM)
Are there any options on the plug-ins I can deselect to keep this feature from being activated?
Thats a silly question that doesn't make sense... you must make the ISO so you can create the CD or DVD of the project... what use would disabling it if then you couldn't create a disk?
Instead look at disabling Symantec Endpoint Protection to see if that allows you to complete the process as it should be completed. For instructions on that, see the documentation that comes with it.
QUOTE (rdsok @ Mar 26 2008, 01:49 PM)
QUOTE (CanOpener @ Mar 26 2008, 01:37 PM)
Are there any options on the plug-ins I can deselect to keep this feature from being activated?
Thats a silly question that doesn't make sense... you must make the ISO so you can create the CD or DVD of the project... what use would disabling it if then you couldn't create a disk?
I am not trying to disable making the ISO. My question was (restated more clearly for the hard of hearing): is there some plugin I selected that is asking for (or using) that cygwin1.dll file? I assume by your silly answer that there is not, and it is failing at some sort of default process to create the ISO file in general. In other words, it is not failing at a point when creating, activating or using a certain plug-in for addition into the program.
Instead look at disabling Symantec Endpoint Protection to see if that allows you to complete the process as it should be completed. For instructions on that, see the documentation that comes with it.
SEPM was disabled earlier as it alerted me to the presence of some naughty tools included in the program (and kept disabling them).. I didn't have to RTFM. I guess 20 years in the industry counts for something! Also, if there is a conflict it is probably passive in nature. SEPM is not actively stopping anything at the ISO building point as there is nothing noted in the program logs .. all 10 of them. However, uninstalling SEPM it is another matter. I guess that is next. Symantec's uninstall for this program is buggy as hell. I guess I will have to RTFM after all.
To totally uninstall NAV (2003 & later) have a look @ this link http://service1.symantec.com/SUPPORT/tsgen...005033108162039
To totally uninstall NAV (pre 2003) have a look @ this link http://service1.symantec.com/SUPPORT/sunse...src=bar_sch_nam
Obviously this is a guess since I'd never use a Symantec product anyway, so this is off the cuff... but I'm not thinking that its blocking something, I think its conflicting in a manner similar to one seen with multiple versions of cygwin installed.
My silly answer was based on your silly question to start with... btw... the cygwin1.dll is part of the ISO creation process.
To totally uninstall NAV (pre 2003) have a look @ this link http://service1.symantec.com/SUPPORT/sunse...src=bar_sch_nam
Obviously this is a guess since I'd never use a Symantec product anyway, so this is off the cuff... but I'm not thinking that its blocking something, I think its conflicting in a manner similar to one seen with multiple versions of cygwin installed.
My silly answer was based on your silly question to start with... btw... the cygwin1.dll is part of the ISO creation process.
QUOTE (rdsok @ Mar 26 2008, 02:49 PM)
To totally uninstall NAV (2003 & later) have a look @ this link http://service1.symantec.com/SUPPORT/tsgen...005033108162039
To totally uninstall NAV (pre 2003) have a look @ this link http://service1.symantec.com/SUPPORT/sunse...src=bar_sch_nam
Obviously this is a guess since I'd never use a Symantec product anyway, so this is off the cuff... but I'm not thinking that its blocking something, I think its conflicting in a manner similar to one seen with multiple versions of cygwin installed.
My silly answer was based on your silly question to start with... btw... the cygwin1.dll is part of the ISO creation process.
To totally uninstall NAV (pre 2003) have a look @ this link http://service1.symantec.com/SUPPORT/sunse...src=bar_sch_nam
Obviously this is a guess since I'd never use a Symantec product anyway, so this is off the cuff... but I'm not thinking that its blocking something, I think its conflicting in a manner similar to one seen with multiple versions of cygwin installed.
My silly answer was based on your silly question to start with... btw... the cygwin1.dll is part of the ISO creation process.
well, there we are, just silly!
I wish it was NAV .. its SEPM. Different monster. Uninstall (I mean, a real uninstall) is only available via their tech support (a special tool that is too powerful to be available to the poor slobs, I mean general public. (I kid you not, that is what symantec is saying on their forums). Trust me, SEPM is a total piece of Bantha poo-doo. Anyway, I will try to install on yet another machine and then try to track this down. Kinda slow at the office, so that means its PLAY TIME! This liitle problem will do nicely. I'll keep this topic thread updated.
That first link was actually for more than just uninstalling NAV but if it didn't list SEPM, I guess its beside the point.
QUOTE (rdsok @ Mar 26 2008, 03:19 PM)
That first link was actually for more than just uninstalling NAV but if it didn't list SEPM, I guess its beside the point.
Well, here is what has worked so far.
I d/l and installed the base cgywin package on the pc in question. It has a cgywin1.dll file dated 3/05/2008. I then replaced both versions of the cgywin1 file that appeared in the UBCD4WIN folder ( a total of 4 files). The error went away and the ISO appeared. I burned it to a CD and boot another computer successfuly to the MAIN BOOT OPTION SCREEN with the program. After chosing the main UBCD4WIN option it ends with a solid blue screen with a mouse cursor. So I fear that replacing those files may have solved the issue, but maybe broke another program that the older cgywin1.dll was in (like C:\UBCD4Win\BartPE\PROGRAMS\cmos and C:\UBCD4Win\temp and two others I can't remember)
Maybe that cgywin1 file (I humbly suggest
) needs to be updated in the next build of UBCD4WIN? I did see by research that the error I was getting (my last log post) was caused by a previous bug in that dll. So the newest version fixed it. Just don't know what I may have broke by doing that file replacement.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.