Error Starting Program

The following message appears after downloading and trying to install
"Iomega Tools Parallel Port Recognition Update":
'The HOTFIX.EXE file is linked to missing
export NTDLL.DLL:aullshr.'
immediately after that a dialog box informs me:
'A device attached to the system is not functioning.'
The reason for all of this:
I just finished installing an iomega zip100 drive without software to go
along with it, because it was a refurbished one, but working allright. So I
went ahead and used the software from my previous, damaged drive, which
completed the job, except for one thing:
In Device Manager I show 'Iomega Parallel Port Interface' with that dreaded
exclamation point on yellow background. It motivated me to to get this
upgrade,
in order to fix it.
What do I do now??

Harry, old and puzzled again.

Harry,

This would suggest that the driver you downloaded was not for Win Me but
perhaps for XP since it is looking for a different version of NTDLL.DLL
than that included as part of Win Me.

BTW I have an external parallel Zip 100 attached to my old Win Me PC here
and have never installed any Iomega software and don't have any problems
with the Iomega Parallel Port Interface. I set it up so long ago though
that I have no idea as to whether I did anything special or not to get it
working. It's late here and unusually I don't have that box running at the
moment but will check it tomorrow morning and see if I can find out what I
did to get everything working.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

The following message appears after downloading and trying to install
"Iomega Tools Parallel Port Recognition Update":
'The HOTFIX.EXE file is linked to missing
export NTDLL.DLL:aullshr.'
immediately after that a dialog box informs me:
'A device attached to the system is not functioning.'
The reason for all of this:
I just finished installing an iomega zip100 drive without software to
go along with it, because it was a refurbished one, but working
allright. So I went ahead and used the software from my previous,
damaged drive, which completed the job, except for one thing:
In Device Manager I show 'Iomega Parallel Port Interface' with that
dreaded exclamation point on yellow background. It motivated me to to
get this upgrade,
in order to fix it.
What do I do now??

Harry, old and puzzled again.

Very good, Mike. Upon my search for an updated driver through 'DriverGuide
Toolkit' I came upon one for Windows ME on Iomega's website and downloaded
it. Before I install, I'll have to find out what I need to do beforehand, in
order to avoid real trouble. That is unless you have a better solution.
I appreciate your concern and help here, as well as always.
Thank you, Mike.

Harry, old and must count some sheep.


"Mike M" wrote in message
...
Harry,

This would suggest that the driver you downloaded was not for Win Me but
perhaps for XP since it is looking for a different version of NTDLL.DLL
than that included as part of Win Me.

BTW I have an external parallel Zip 100 attached to my old Win Me PC here
and have never installed any Iomega software and don't have any problems
with the Iomega Parallel Port Interface. I set it up so long ago though
that I have no idea as to whether I did anything special or not to get it
working. It's late here and unusually I don't have that box running at the
moment but will check it tomorrow morning and see if I can find out what I
did to get everything working.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

The following message appears after downloading and trying to install
"Iomega Tools Parallel Port Recognition Update":
'The HOTFIX.EXE file is linked to missing
export NTDLL.DLL:aullshr.'
immediately after that a dialog box informs me:
'A device attached to the system is not functioning.'
The reason for all of this:
I just finished installing an iomega zip100 drive without software to
go along with it, because it was a refurbished one, but working
allright. So I went ahead and used the software from my previous,
damaged drive, which completed the job, except for one thing:
In Device Manager I show 'Iomega Parallel Port Interface' with that
dreaded exclamation point on yellow background. It motivated me to to
get this upgrade,
in order to fix it.
What do I do now??

Harry, old and puzzled again.

Harry,

I honestly can't remember what I did and thought that Win Me included
support for a Zip 100 attached to a parallel port but now think I am
probably mistaken.

I can't see that you will have any problem if you download and use the Win
Me parallel port interface driver from the Iomega site
(iodrv-wme-x86-403.exe). The trick as I seem to recall (it was a long time
ago) was to get the best set up for your system by setting the correct
switches..

I think that I must have configured my old Win Me box by copying the
installation file (ppa3.inf) and miniport driver (ppa3.mpd) from somewhere
else and then installed the driver by pointing it at a folder containing
just those two files. I've just checked the settings on the Settings tab
on the Parallel Port Interface in the Device Manager and see that I have
it set as follows:
mode epp /port 378 /speed 6
378 is the address of my parallel port which I have configured in the bios
as ecp/epp but the meaning of the /speed switch and why I have it set to 6
is way beyond my memory. Perhaps a visit to the Iomega site is called
for. I haven't been there for years other than last night to see if they
had a simple Win Me Zip driver, which they did.

Cheers,
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

Very good, Mike. Upon my search for an updated driver through
'DriverGuide Toolkit' I came upon one for Windows ME on Iomega's
website and downloaded it. Before I install, I'll have to find out
what I need to do beforehand, in order to avoid real trouble. That is
unless you have a better solution.
I appreciate your concern and help here, as well as always.
Thank you, Mike.

You don't have to anymore, Mike.
I downloaded and installed the file you mentioned and it installed
successfully because, before I did, I removed that dreaded SCSI warning and
don't need it either.
The Zip drive shows up and works perfectly, what more do I want.
Thanks so much for your precious help, Mike.

Harry, old and on even keel now.


"Mike M" wrote in message
...
Harry,

I honestly can't remember what I did and thought that Win Me included
support for a Zip 100 attached to a parallel port but now think I am
probably mistaken.

I can't see that you will have any problem if you download and use the Win
Me parallel port interface driver from the Iomega site
(iodrv-wme-x86-403.exe). The trick as I seem to recall (it was a long time
ago) was to get the best set up for your system by setting the correct
switches..

I think that I must have configured my old Win Me box by copying the
installation file (ppa3.inf) and miniport driver (ppa3.mpd) from somewhere
else and then installed the driver by pointing it at a folder containing
just those two files. I've just checked the settings on the Settings tab
on the Parallel Port Interface in the Device Manager and see that I have
it set as follows:
mode epp /port 378 /speed 6
378 is the address of my parallel port which I have configured in the bios
as ecp/epp but the meaning of the /speed switch and why I have it set to 6
is way beyond my memory. Perhaps a visit to the Iomega site is called
for. I haven't been there for years other than last night to see if they
had a simple Win Me Zip driver, which they did.

Cheers,
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

Very good, Mike. Upon my search for an updated driver through
'DriverGuide Toolkit' I came upon one for Windows ME on Iomega's
website and downloaded it. Before I install, I'll have to find out
what I need to do beforehand, in order to avoid real trouble. That is
unless you have a better solution.
I appreciate your concern and help here, as well as always.
Thank you, Mike.

Sounds good Harry.

Out of curiosity what switch settings did your system set up for the
parallel port interface? You can check this by opening the Device
Manager, opening the Properties sheet for the Parallel Port Interface and
checking on the Settings tab.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

You don't have to anymore, Mike.
I downloaded and installed the file you mentioned and it installed
successfully because, before I did, I removed that dreaded SCSI
warning and don't need it either.
The Zip drive shows up and works perfectly, what more do I want.
Thanks so much for your precious help, Mike.

No Parallel Port Interface Settings, Mike.
I don't seem to need them.
My property sheet is for "Iomega Zip100".
The settings are as follows:
Target ID: 0
Logical Unit: 0
Firmware revision: 03.H
Options:......./ and Drive letter: E (my third drive for
now, with C being the harddrive and D the CD-ROM)
Driver Provider: Standard disc drivers
date: 06/08/2000 and digital signer:
Microsoft Consumer Windows Publisher.
Apparently that is doing the trick for me and I couldn't ask for more right
now, Mike.

Harry, old and needs no coffee.


"Mike M" wrote in message
...
Sounds good Harry.

Out of curiosity what switch settings did your system set up for the
parallel port interface? You can check this by opening the Device
Manager, opening the Properties sheet for the Parallel Port Interface and
checking on the Settings tab.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

You don't have to anymore, Mike.
I downloaded and installed the file you mentioned and it installed
successfully because, before I did, I removed that dreaded SCSI
warning and don't need it either.
The Zip drive shows up and works perfectly, what more do I want.
Thanks so much for your precious help, Mike.

Are you saying that the iodrv-wme-x86-403.exe drivers don't add an Iomega
Parallel Port Interface entry to the SCSI controllers section of the
Device Manager? If so it would appear that Iomega must have totally
rewritten their driver interface which I find somewhat unexpected. BTW
I'm not interested in the Zip 100 settings in the Disk drives section,
it's the controller I'm interested in.

I guess I really should have a look at the new drivers and try installing
them on the Win Me box here that has an external Zip 100 drive.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

No Parallel Port Interface Settings, Mike.
I don't seem to need them.
My property sheet is for "Iomega Zip100".
The settings are as follows:
Target ID: 0
Logical Unit: 0
Firmware revision: 03.H
Options:......./ and Drive letter: E (my third drive for
now, with C being the harddrive and D the CD-ROM)
Driver Provider: Standard disc drivers
date: 06/08/2000 and digital signer:
Microsoft Consumer Windows Publisher.
Apparently that is doing the trick for me and I couldn't ask for more
right now, Mike.

No controller here, Mike, that's what I am saying all along
and that's what I found so strange. But, why care? The "ZIP" works and
really nice, too, so I am leaving well enough alone, right?
I fully understand you being interested in the technical details, but why
should I be?
Maybe an e-mail to Iomega would be in order for you to get the information
you are looking for.
My next project will be *Partitioning*, but in due time.
Thanks, Mike.

Harry, old and getting older by the day.


"Mike M" wrote in message
...
Are you saying that the iodrv-wme-x86-403.exe drivers don't add an Iomega
Parallel Port Interface entry to the SCSI controllers section of the
Device Manager? If so it would appear that Iomega must have totally
rewritten their driver interface which I find somewhat unexpected. BTW
I'm not interested in the Zip 100 settings in the Disk drives section,
it's the controller I'm interested in.

I guess I really should have a look at the new drivers and try installing
them on the Win Me box here that has an external Zip 100 drive.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

No Parallel Port Interface Settings, Mike.
I don't seem to need them.
My property sheet is for "Iomega Zip100".
The settings are as follows:
Target ID: 0
Logical Unit: 0
Firmware revision: 03.H
Options:......./ and Drive letter: E (my third drive for
now, with C being the harddrive and D the CD-ROM)
Driver Provider: Standard disc drivers
date: 06/08/2000 and digital signer:
Microsoft Consumer Windows Publisher.
Apparently that is doing the trick for me and I couldn't ask for more
right now, Mike.

I must add one thing to my last post, Mike:
Under "Hard Disc Controllers" are two device icons listed with no
description, but both working properly.
When I tried to update the driver (unknown) with the file you provided, it
failed because it already is in use, I presume.
Just to give you all the info I have, Mike.

Harry.


"Webster72n" wrote in message
...

No controller here, Mike, that's what I am saying all along
and that's what I found so strange. But, why care? The "ZIP" works and
really nice, too, so I am leaving well enough alone, right?
I fully understand you being interested in the technical details, but why
should I be?
Maybe an e-mail to Iomega would be in order for you to get the information
you are looking for.
My next project will be *Partitioning*, but in due time.
Thanks, Mike.

Harry, old and getting older by the day.


"Mike M" wrote in message
...
Are you saying that the iodrv-wme-x86-403.exe drivers don't add an
Iomega
Parallel Port Interface entry to the SCSI controllers section of the
Device Manager? If so it would appear that Iomega must have totally
rewritten their driver interface which I find somewhat unexpected. BTW
I'm not interested in the Zip 100 settings in the Disk drives section,
it's the controller I'm interested in.

I guess I really should have a look at the new drivers and try
installing
them on the Win Me box here that has an external Zip 100 drive.
--
Mike Maltby MS-MVP [2001-2004]



Webster72n wrote:

No Parallel Port Interface Settings, Mike.
I don't seem to need them.
My property sheet is for "Iomega Zip100".
The settings are as follows:
Target ID: 0
Logical Unit: 0
Firmware revision: 03.H
Options:......./ and Drive letter: E (my third drive for
now, with C being the harddrive and D the CD-ROM)
Driver Provider: Standard disc drivers
date: 06/08/2000 and digital signer:
Microsoft Consumer Windows Publisher.
Apparently that is doing the trick for me and I couldn't ask for more
right now, Mike.