Don't have access to the colleague's machine, but my file was last modified June of 2003. Same with one of the computers the software will install on, so there doesn't seem to be a difference there.
Printable View
Don't have access to the colleague's machine, but my file was last modified June of 2003. Same with one of the computers the software will install on, so there doesn't seem to be a difference there.
OK Angelic~
I still haven't made up my mind if this is a hardware or software problem? so here are another few tests I would like you to try.
Can you make a mirror of the installation CD and either load it onto your folder on the network drive, or e-mail it to yourself and launch it from there...............if it installs from either of those, I would say certainly hardware.
Otherwise, can you get hold of another CD drive (internal/external, it doesn't matter) insert that into your machine and try it then.
I have seen CD drives accept some CDs and not others, and not be consistent............they usually die a few weeks/months later?
Also, can you try burning a copy at 4x (four speed) or maybe 8x...............that sometimes works, but warns you that the CD drive is on the way out.
Good luck and stick at it!
:D
Finally...an update! I had all but given up on this problem when I finally figured out what dll's the software installs/alters in the system32 directory:
urlmon.dll
hlink.dll
oleaut32.dll
schannel.dll
So I bet following these files will give me a clue, perhaps?
Hi Angelic~
Take a look at them all on a machine that works, and one that doesn't. Clue: copy onto floppy or CD (that would depend on size) and load them onto a 95/98/ME machine.
Then go to:
<start>
<run>
and type in winfile.exe or maybe just winfile
From the old DOS file manager you can check the file sizes to the actual byte.
I will go for oleaut32.dll...............but that is just me :D
Good luck, and many thanks for getting back with an update.........so many threads just seem to "die"
Cheers