Select Netware Logon

[Jason]

After FBA runs and I login, I always get a dialog box for Netware logon
server, until I remove the netware protocol.

Apparently I've got Netware in my SLX image somewhere. What component,
files do I need to remove from my SLx file, so I don't have to bother with
Netware.

Thanks
Jason

 

[KM]

Jason,

"Client Services for NetWare"
"Ipx / Spx Transport Stack"
"Netnwlnk Inf"

 

[Sean Liming \(eMVP\)]

Component dependencies being what they are, you might have to remove the
following component so the Netware components KM lists are not pulled in:

Networking Application Compatibility
Help and Support Services
Active Directory Service Interface (ADSI) Netware 3.x Provider
Active Directory Service Interface (ADSI) Novel Directory Service Provider

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
XP Training Class Nov 28-30 - http://www.sjjmicro.com/Training.html

 

[Guest]

Jason,

Component dependencies go a lot deeper than Sean mentioned. If you check
dependencies, even with additional components removed, they still get pulled
back in ("Help and Support Services " depencency with "System Restore Core")

Joe

 

[Sean Liming \(eMVP\)]

That is correct. I only looked at the immediate component dependencies.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
XP Training Class Nov 28-30 - http://www.sjjmicro.com/Training.html

 

[Jason]

The dependencies do go pretty deep, and I'm going to assume that by removing
all of them, it will probably affect other things as well. I'll just leave
it in my SLX file and after FBA runs, I'll uninstall Netware from Network
properties.

Thanks

 

[KM]

Jason,

Deep dependency chain was the reason I only posted components that are directly related to the protocol you asked about.
It won't break anything else if you disable to remove those 3 components in your config and will leave with a few known errors
(Tasks) in the DependencyChecker log.