
Finally....fixed the problem !!
Bit of an odd ball really unless it's just me being an idiot (would love to hear your comments though).
o.k. here we go
I was having a look in the mamewah log file & noted the command that mamewah was sending to the mame.exe so I cut/pasted this into a run command & nothing happened apart from the dos box flashed for a few seconds. I then thought, hold on a minute it's trying to open a rom file in mame(dos versions) default & NOT the folder that i have configured the mamewah mame.ini to look in. The reason i chose an alternative rom pathname was becuase i've been using mame32 (which obvously has it's own rom folder) & that's were all my roms lived .
So....i copied x1 rom from the mame32 rom folder to the mame (dos version) rom folder & guess what....it all works. As i still like to use mame32 (for rom browsing speed) i'm hoping that i can point mame32 to the mame (dos versions) rom folder becuase i really don't was x5000 roms sitting in duplicate folders eating up my HDD.
The above only seems to effect the rom folder i.e Artwork, Cabinets etc can live anywere.
I'd love to hear your thoughs on this especially if there's an easier quick fix .ini file amendment that i could do instead.