Re: Still hosed by setup problem LAID TO REST (Sorta)
Well, in desperation I took the final step and blew away the only thing left after my previous rampage -- the Windows Registry entries. I pretty much made my installation look as though it had never heard of Cygwin. OK. I was now able to run Setup to completion. Of course, I am nowhere near back where I started -- I also lost any customization I had ever done and other things as well. But, at least, I do have a working installation even though it sometimes isn't working the way I expect. Of course, this suggests the problem was with some registry entry. I can't see anything weird about mine, the only thing is that I have my disks partitioned very much like a Linux system ( it will dual-boot someday RSN ). That means things like /tmp and /var ( but NOT CygwinRoot ) were mounted on the root of some partitions just as they are of necessity in Linux. It worked great for me - mentally - but maybe it is a gotcha during installation. Bas van Gompel wrote: Op Tue, 12 Oct 2004 18:55:25 -0400 schreef David A. Cobb in [EMAIL PROTECTED]: : Well, now I am completely out of business! : : This is more data regarding the URL Scheme Not Registered failure in : SETUP, last reports were around 9/18. : : In the last progress message posted before the crash, I spotted a : package name (from gnome) that was one character short at the left-hand This happens if a package is in the same directory as the ini-file. eg: ``install: packagename_without_slashes-1.0-1 ...'' causes setup to display: ``ackagename_without_slashes-1.0-1'' (A patch for this was submitted by me several months ago, but never reacted upon...) If the string is left empty, an attempt to allocate -1 bytes is made... [...] : Then Install from Local Directory -- BANG it immediately crashes with : the URL Scheme Not Registered error. This /might/ be caused by the above. (Who knows what happens if you try to allocate a negative amount of memory.) try: find -name setup.ini |xargs -r grep '^install: *$' in your package-dir (if you ever get a working installation). [...] Good luck. L8r, Buzz. -- David A. Cobb, Software Engineer, Public Access Advocate By God's Grace, I am a Christian man; by my actions a great sinner. -- The Way of a Pilgrim: R.French, Tr. Life is too short to tolerate crappy software! begin:vcard fn:David A. Cobb n:Cobb;David A. adr:;;7 Lenox Av #1;West Warwick;RI;02893-3918;USA email;internet:[EMAIL PROTECTED] title:Independent Software Consultant note:PGP Key ID#0x4C293929 effective 01/28/2004 x-mozilla-html:TRUE version:2.1 end:vcard
Re: Still hosed by setup problem LAID TO REST (Sorta)
Larry Hall wrote: At 09:01 AM 10/29/2004, you wrote: SNIP/ Of course, this suggests the problem was with some registry entry. I can't see anything weird about mine, the only thing is that I have my disks partitioned very much like a Linux system ( it will dual-boot someday RSN ). That means things like /tmp and /var ( but NOT CygwinRoot ) were mounted on the root of some partitions just as they are of necessity in Linux. It worked great for me - mentally - but maybe it is a gotcha during installation. If by mounted on the root of some partitions you mean your '/' is mounted on 'c:\', for example, don't waste any time contemplating the problems with that. I do this all the time on many machines and it's no problem for Cygwin. It's only a problem for users if they like to mix and match multiple GNU tool sets and aren't careful about it. Nah, I'd seen the warnings on that and didn't care to take a chance. '/' - F:\Cygwin\ '/tmp' - T:\... did I mention this is WinXP, so I got to play around a bit with the Drive letters. '/var' - V:\ --- this drive is Fat32 and is visible as 'mount --bind --type VFAT' at places within the Linux /var filesystem '/home' -- H:\HOME probably a few other peculiarities I've attached the HKLM registry entries that I exported before I wiped it all out. I know this isn't a plausible explanation for the problems I saw. The speculation above about something with a length = -1, which sounds like a good recipe for a buffer overflow/underflow to me, seems better. But then, why would starting from absolute zero make any difference? -- David A. Cobb, Software Engineer, Public Access Advocate By God's Grace, I am a Christian man; by my actions a great sinner. -- The Way of a Pilgrim: R.French, Tr. Life is too short to tolerate crappy software! REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions] [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin] [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2] cygdrive prefix=/mnt cygdrive flags=dword:002a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/] native=F:\\Cygwin2 flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/bin] native=F:\\Cygwin2\\bin flags=dword:004a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/debian] native=V:[EMAIL PROTECTED] flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/Floppy] native=A: flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/home] native=H:\\HOME flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/home/root] native=C:\\HOME\\root flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/mnt/WIN_XFR_B1] native=D: flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/pub] native=S:\\Shared\\Documents flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/root] native=C:\\HOME\\root flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/root/logs] native=D:\\logs flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/Shared] native=S:\\Shared\\Documents flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/sys] native=C:\\WINDOWS flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/tmp] native=T: flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin] native=F:\\Cygwin2\\bin flags=dword:004a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/doc] native=S:\\Cygwin\\usr\\doc flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib] native=F:\\Cygwin2\\lib flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/local/src] native=H:\\Cygwin\\usr\\local\\src flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/share/doc] native=S:\\Cygwin\\usr\\share\\doc flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/share/xemacs] native=F:\\WinApps\\XEmacs flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/src] native=H:\\Cygwin\\usr\\src flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/X11R6/lib/X11/fonts] native=F:\\Cygwin2\\usr\\X11R6\\lib\\X11\\fonts flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/var] native=V: flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/var/cache/Cygwin] native=V:\\cache\\net\\c\\Cygwin\\Repository flags=dword:000a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/WinApps] native=F:\\WinApps flags=dword:001a [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
Re: Still hosed by setup problem
Op Tue, 12 Oct 2004 18:55:25 -0400 schreef David A. Cobb in [EMAIL PROTECTED]: : Well, now I am completely out of business! : : This is more data regarding the URL Scheme Not Registered failure in : SETUP, last reports were around 9/18. : : In the last progress message posted before the crash, I spotted a : package name (from gnome) that was one character short at the left-hand This happens if a package is in the same directory as the ini-file. eg: ``install: packagename_without_slashes-1.0-1 ...'' causes setup to display: ``ackagename_without_slashes-1.0-1'' (A patch for this was submitted by me several months ago, but never reacted upon...) If the string is left empty, an attempt to allocate -1 bytes is made... [...] : Then Install from Local Directory -- BANG it immediately crashes with : the URL Scheme Not Registered error. This /might/ be caused by the above. (Who knows what happens if you try to allocate a negative amount of memory.) try: find -name setup.ini |xargs -r grep '^install: *$' in your package-dir (if you ever get a working installation). [...] Good luck. L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re
