Board index » delphi » Legacy 16 bit Applications ... DLL Dependency

2005-05-22 10:44:48 PM
delphi199
Hi,
After migrating over to XP a while ago now, I had to stop using Borland's
Resource Workshop as it complained that it 'Can't run 16-bit Windows
program' ... + 'Cannot find file xxxx (or one of its components) ...'.
Anyway, the other day I accidently loaded a lot of old code onto my laptop
(also running XP) and ended up with Workshop installed. For old time's
sake, I started the application and lo and behold it runs on my laptop !
I've tried in vain to identify what I am missing on my development system ...
is there a tool that I can use that is equivalent to MS dependency walker
for 16 bit applications or some other way to ascertain what DLL is missing ?
(Don't you hate messages ... 'File not found' without elaborating further).
(Oddly enough, a real old game "Chip's Challenge" runs on my development
systems but not my laptop !)
Andrew
 

Nothing to do with dlls at all ... forgot that these apps can not deal with
long folder names !
Andrew
 

Thanks ... no, it was just one of those things that was niggling me as I
couldn't understand why it worked on my laptop ... more of a puzzle rather
than the need to use such an antiquated tool !
Andrew
"Ingvar Nilsen" <XXXX@XXXXX.COM>writes

Andrew Jameson writes:
except long file names then <g>
--
Ingvar Nilsen
www.ingvarius.com
 

I haven't tried this with 16 bit programs is definitely worth a shot.
Try loading Process Explorer by SysInternals on your laptop - select the
resource workshop process in the process list. On the view menu make
sure that show lower pane is selected and choose DLLs as the lower pane
view. I believe that shows you all the dlls in use by that process.
Let me know if that does/doesn't work. In any case I find process
explorer indispensable for other tasks as well and wonder how I survived
with the feeble task manager for so long.
-Michael Zeringue
Andrew Jameson writes:

Thanks for that tip ... Process Explorer is really useful but in this case
it does not reveal what DLLs are failing to load ... but the real answer
lies in the fact that I have got it installed on an NTFS drive with 8.3 format
disabled and then with long filenames ... so it doen't know where it is !
Andrew
 

Oliver Townshend