I've got SSS and DIS working fine however when I try to run INPA all I get is a blank screen with the f-buttons along the bottom.
When I REMOVE system variable then it loads farther but I get all kinds of errors.
I am running windows XP sp3.
Here's a screenshot of what I get:
Last edited by firehawk618; 03-22-2011 at 02:18 AM.
you need to install the second halve of INPA, you have installed the "operating system" now you need to install the "program", the how to is in the instructions
This often happens when you attempt to install INPA from the desktop instead of a disk. For some reason some files don't extract properly and you are left with an incomplete installation.
start instprog again and use Rectification programs as installation profile
Which rectification? I did the UK one already.
Last edited by firehawk618; 03-22-2011 at 02:18 PM.
Any follow up on this?
After finally completing an install with no dll errors or anything, INPA starts, but I also have a totally blank screen.
A post above here suggest that you need to install the "second" half, but no install instructions mentions anything like that.
1998 BMW M3 3.2 Cabrio Alpinweiί III on Schwarz German spec 1 of 12
SMG SRA PDC AUC OBC GSM HK UURS IHKA FGR MFL
IG: https://www.instagram.com/iflok/
Run INPA using INPA(_.IPO).
I have no idea what you mean. There is no file named INAP._ipo if that is what you mean.
In the meantime I found out it runs just fine on my old XP PC, but my netbook is running Win7 Pro (32bit) and I think that is the problem.
I tried installing from a virtual CD drive and/or with compatability set to Win XP and run as admin, but all the same result.
What's weird though is if I add a c:\inpa\bin to the environmental virable Path, Inpa does load with all the info on screen, but then throws all kinds of API errors.
After deleting that path so only EDIABAS\BIN is left, I get the blank screen.
1998 BMW M3 3.2 Cabrio Alpinweiί III on Schwarz German spec 1 of 12
SMG SRA PDC AUC OBC GSM HK UURS IHKA FGR MFL
IG: https://www.instagram.com/iflok/
The reason you are getting API errors is that your computer cannot find EDIABAS, which should be installed directly on c: drive. The correct path variable that needs to be added is ;c:\ediabas\bin and the only thing that can affect this is where your hard drive is located on a drive other than c: drive or if EDIABAS has been installed inside another folder rather than directly onto c: drive.
That's the weird thing, as Inpa, NCS Expert and Ediabas are all directly on C:\, which is their default install location.
As said, I already had c:\ediabas\bin set in the Path variable. When I delete that, nothing works.
The install on my XP pc is Identical to the one under Win7 32bits and that works just fine from the first try. So the only difference is the OS.
1998 BMW M3 3.2 Cabrio Alpinweiί III on Schwarz German spec 1 of 12
SMG SRA PDC AUC OBC GSM HK UURS IHKA FGR MFL
IG: https://www.instagram.com/iflok/
If the install on the XP machine is fully functional, do a direct copy of all the BMW related folders (ie, NCSEXPERT) onto your windows 7 machine. Overwrite all the folders/files. I've done this before and it works like a charm. The only problem you may run into is if you set your cable on different comm ports. Even then, you just need to change that value to what's on your XP machine.
XP is a pc so not portable. It was just to test I got the install right.
i have a yellow GT1 head. I don't use comm ports.
1998 BMW M3 3.2 Cabrio Alpinweiί III on Schwarz German spec 1 of 12
SMG SRA PDC AUC OBC GSM HK UURS IHKA FGR MFL
IG: https://www.instagram.com/iflok/
Fixed the blank screen. After doing some intense Google searching, I found a massive INPA/EDIABAS/NCS FAQ document.
http://forum.b-m-w.ru/index.php?acti...downfile;id=44
The part about "I have a blank screen" provided the solution:
Reason 1: The api.dll or api32.dll file has been manually copied into the WINDOWS
directory with Windows XP and into the WINNT directory with Windows NT.
Solution 1: Delete the file api.dll or alternatively api32.dll from the WINDOWS or alternatively
the WINNT directory. The file may only exist in the directory \EDIBAS\BIN\.
I didn't find an API.DLL/API32.DLL in my Windows folder at first, then noticed that it did exist in \\windows\system32
After I renamed the extension to "delete" the file, INPA fired up correctly right away.
So if anyone has the same problem and tried everything mentioned like I did, this may be your solution.
1998 BMW M3 3.2 Cabrio Alpinweiί III on Schwarz German spec 1 of 12
SMG SRA PDC AUC OBC GSM HK UURS IHKA FGR MFL
IG: https://www.instagram.com/iflok/
God bless ya man.
Bookmarks