Hi, as I can detect the incompatibility mentioned in the installation notes, to know when to use the option -E0? thanks!
Hi Andrés , If any of QNX4 drivers (Fsys.atapi, Fsys.ahci, io-usb, network drivers, etc.) terminates by SIGSEGV (at 00D1:XXXXXXXX) then one of the possible reason is incompatible PCI BIOS. Example of such problem: http://community.qnx.com/sf/discussion/do/listPosts/projects.qnx4/discussion.general.topc21160?_pagenum=3 Regards, Pavel > Hi, as I can detect the incompatibility mentioned in the installation notes, to know when to use the option -E0? > > > thanks! > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post91594 > >
We have a server in which falls the Net Case: http://community.qnx.com/sf/go/post90417 It may be also one of the cases? If not you can have some adverse effect? thank you very much!, Andres
Hi Andrés, I don't think that Proc32 option -E0 would have adverse effect on your system but unfortunately it wouldn't help you. In your situation I only can recommend to try latest Net drivers or try another network hardware if it is possible. To clarify situation with new Proc32 option -E0: You should use -E0 option only if you can't run QNX because drivers (Fsys drivers, io-usb, Net drivers) terminates by SIGSEGV (in most cases at 00D1:XXXXXXXX) when they try to detect PCI devices. Regards, Pavel > We have a server in which falls the Net > Case: http://community.qnx.com/sf/go/post90417 > > It may be also one of the cases? > If not you can have some adverse effect? > > thank you very much!, > Andres > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post91600 > >
