I found the problem, I made a mistake in the I/O configuration and started mapping the I/O of that device from 2501 instead of 2500!! I didn't know that not mapping an i/o would have triggered that kind of error...
Fixed that, fixed everything!
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!