(2) The SCSI/SATA driver might be wrong, but it seems like the laptop should at least show the file on the floppy when it gets to that point in the installation. The reason for the driver question is: I've been reading the "mk" version of the toughbook wrong. It's a CF-532Jxxxxx which means that it's a MK4, not a MK2. Panasonic never released the MK4 with XP and does not list drivers for XP (the minimum O.S. released with the MK4 product was Windows 7. If they changed the SCSI/SATA chip, the MK2 XP SCSI/SATA driver likely won't work (and I don't know what chip they use - I haven't opened the toughbook yet). It may be the case that I'll need a different laptop (CF-53 mk2 or CF-52 or earlier) to run XP natively. If I can't get XP loaded natively and there's a straightforward way to get XP virtualized under Windows 7 Home Premium 32-bit (I might have a 7 pro disk and COA lying around if it's needed), I'd be willing to put in the effort, although I've had trouble getting the USB 2 and 3 drivers to install. I'll let y'all know how it goes this weekend. Thank you for the help so far!
IBM ThinkPads always had relatively good UNIX support and it seems the hardware configuration of the IBM T30 is not too dissimilar from the Group Tester One. With some tweaks it can be made to work. So far I haven't heard of anyone getting it to work (native) on anything else than a ThinkPad but that doesn't mean there aren't other computers that could run it. Computers of the same time period obviously have a greater chance of success than newer and older ones. If you have a spare harddisk (or don't mind reinstalling Windows from scratch), feel free to try and see what happens... - > Thanks. I might just go get a T30 and see how it goes - they're not expensive. So many variables with different brands and models and still having issues with the D630, but better progress than before.Progress:
BUT... even with Virtualization enabled in BIOS, VMware throws a "Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized VT-x/EPT?" warning. "Yes" is the only way to continue ("No" ends the session). Edited the session config file (located at the bottom of the VMware session window) to turn off virtualized VT-x/EPT: vmv.enable ="FALSE" VMware now runs without an error, but warns that only 32-bit virtualized sessions are allowed now. Figured that isn't an issue, but IDK 100%.
Ran into some confusion about the IP address for DIS vs. the Laptop's IP address when using the ADS/OBD head (tinyADS w/cable from openlabs.co - yeah, I was lazy and bought the pre-assembled cable... ). The IP thing might be biting me in the butt right now, but on to the INPA installation because we need it for DIS...
At this point, the ADS head is *not* connected to the vehicle (6/94 840ci or 840i, depending on who you ask).
4a) Deleted the VMware session, reinstalled it as Workstation 6 and EXSi5. Why EXSi5? IDK, seemed like something to try. Workstation 6.5+ drops IDE support when configuring the session, and since the instructions call for the HD at IDE 0:0 and CD/DVD at 1:0, I didn't want to go too far off the reservation and change more than one thing at a time. So, DIS and DATEN reloaded on EXSi5. laptop rebooted, still the same IP address question to resolve (maybe?), ran ifhsrv32.exe, started DIS.
20200319_142053.jpg 20200319_142056.jpg 20200319_125638.jpg 20200319_142427.jpg Last edited by DavesNotHere; 03-19-2020 at 04:00 PM.Reason: loaded photos -
The Coding screen in the previous post "works" in that the buttons are clickable and I can navigate back to the DIS home screen or anywhere else. Once Diagnostics is clicked, DIS hangs. Putting some more time on this after I check it out on the car first. - > Originally Posted by DavesNotHereThanks. I might just go get a T30 and see how it goes - they're not expensive. So many variables with different brands and models and still having issues with the D630, but better progress than before. Not so fast... If you want a native install you also need a DK (yellow head) interface. Genuine ones are hard to come by and very expensive. Even clones are quite pricey.
It's probably okay as it is now (DIS is not 64-bit and the fact that you can actually launch it proves that VMWare works), but this seems to be a common issue on Dell laptops. Apparently you do not only have to enable Intel VT-x in the BIOS but also through Dell Client Configuration ToolKit (CCTK). From what I've found you should execute following CLI commands: cctk -virtualization=disable (reboot) cctk -virtualizaton=enable
Instead of using physical media, simply change the properties of the CD/DVD drive in VMWare: Select "Use ISO image file" instead of "Use physical drive" and click "Browse..." to locate and load the ISO file. Anyway, for now forget about INPA, Ediabas, ifhsrv32.exe and the ADS interface. Even without those you should still be able to at least access the DIS Diagnosis home screen. As long as that doesn't work it makes no sense to make things more complex by introducing Ediabas and ADS. 4a) Deleted the VMware session, reinstalled it as Workstation 6 and EXSi5. Why EXSi5? ESXi support shouldn't matter if you use VMWare Workstation, but it's fine. I have the same setting.
An SSD might improve loading times a bit but don't expect wonders. The main problem of DIS in a virtual machine is that there are no VMWare drivers for SCO OpenServer 5.0.6. That means it accesses the (virtual) harddisk in a low speed compatibility mode instead of making better use of the hardware capabilities. The same is true for the graphics. This is where a native install has a clear advantage. It'll run a lot faster on even slower hardware. You can compensate for the lack of VMWare drivers by using very powerful hardware. On a modern high-end system you can get DIS to boot to the home screen in under 40 seconds in VMWare. HOWEVER... DIS gets stuck when opening the "Diagnosis" page. The hourglass never goes away and no buttons or scroll features are functional. And that shouldn't happen... Even without an interface connected you should be able to access the Diagnosis home screen (beyond that you need actual connection to a vehicle). I also noted a portmapper error when DIS starts Some warnings and errors during startup are normal (like PCI to Cardbus bridge not found, UHCI/OHCI controller not found,...). These point at hardware that is not present in the virtual machine but is otherwise not required for normal operation. Portmapper errors usually indicate network issues and DIS is extremely fragile when it comes to networking. I also see references in your pictures to devices that should not exist in the virtual machine. Are you sure you followed the instructions to the letter? Can you reinstall DIS, carefully paying attention to the prerequisites of the virtual machine, and stop right before "Change DIS IP Address". Instead check if you can now access the Diagnosis home screen without the hourglass getting stuck. -
"Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized VT-x/EPT?" warning. Oh well, it was worth a shot - can always disable the warning.
FWIW: The laptop chime seems loudly hung at the screen to Restart, but it can be silenced with CTL-ALT-F12. The first time this happened yesterday, I forced a laptop shutdown by holding the power key due to GF aggro and slamming doors... not so bueno. I had reinstalled with all the noise but using CTL-ALT-F12 yesterday before posting about the issues then. The seemingly hung chime still is a thing though.
Again, nothing is clickable and this time the Space Bar does nothing. CTL-ALT-F12 shuts down the session and it restarts to DIS and Diagnose like this: 20200320_140652.jpg 20200320_140714.jpg where nothing is clickable, the Space Bar does nothing, and the cursor is an hourglass. Last edited by DavesNotHere; 03-20-2020 at 05:06 PM.Reason: Added photos, finished post - > On a whim - I loaded the Toughbook 53 mk4 with Windows 7 32-bit. Installed VMware, DIS, and the Daten from the ISOs. Same result as above. Seems to be "okay" until launching Diagnostics, then it hangs the same as above.Moving forward: Loaded INPA and the tools from the ISO, set compatibility to XP SP3, and INPA runs. I'll test it on the car when it stops raining tomorrow. Still looking for a DIS solution, but having INPA running will help a bunch. Thinking about digging up the DIS image I had and loading that to see if something at least changes. I'll post on this again soon. > Originally Posted by DavesNotHere
You should not add a serial port to the DIS virtual machine (although I can't see this causing the problem, computers like the Group Tester One and IBM T30 have a serial port too). DIS does not support serial interfaces. The way the ADS/ODB interface works in DIS is actually through ifhsrv32.exe (Ediabas) in Windows. ifhsrv32.exe in Windows talks to the interface over a serial port but the communication with DIS is actually over network. Thus the virtual machine does not need a serial port. I didn't see how to unmount the .iso before "restart the system", so I used CTL-ALT-F12 and shutdown the session. Sorry for the confusion there. There is not really a way to unmount the image in VMWare other than loading another ISO, disconnecting (disabling) the CD/DVD device or changing it back to the physical device. I typically use a small empty dummy.iso for this. FWIW: The laptop chime seems loudly hung at the screen to Restart That's normal. Whomever developed the original installer at BMW really seemed to like the system beep. Anyway, judging from your screenshots there is still something wrong with your network configuration. Immediately after installing DIS the network status in the top right corner of the screen should look as follows: Yours stays grey (when changing DIS to use the ADS/ODB interface it's normal these become grey again but not at this stage of the installation). The portmapper error is probably related to this and I'm pretty sure this is what prevents you from starting Diagnosis (remember, DIS is extremely fragile when it comes to networking). What is the IP address of the Windows machine? Is there any chance you have a network conflict with the default IP address of DIS (192.168.68.30 - not really a common range for home networks)? -
I took the liberty of setting up VMnet2 on the Dell's wired NIC and used that for the Network Adapter "Custom (VMnet2)". VMnet0 uses the Wifi adapter. No difference either way or Bridged - the network lights stay grey in DIS. I agree that it looks like the problem lies with the portmapper and the PCNet - PCI bridge pnt0 device that is failing (missing) during the session boot. I don't know how to fix that within VMware (how to get to the O.S. with DIS loaded to work on devices) without having the PC running UNIX in front of me to build a working VMware session from. But one foot in front of the other; back to Bridged and continuing with this. Very much appreciating your help. Last edited by DavesNotHere; 03-25-2020 at 03:13 PM. - > Originally Posted by DavesNotHereThe mask when changing the DIS address should be 255.255.255.0, yes? Yes, but don't change the DIS address or interface yet (during your next install). First check whether you get the green/yellow/red bar right after installing DIS and can access the Diagnosis screen without things locking up. It doesn't make sense to proceed with the instructions if it already fails right there. > To date: The bar does not light up after the CD and does not light up after the reboot or after the DVD and before changing the network address (I have yet to see it light up at all). Doing another install - maybe on VMnet1 or 8 since they show up in ipconfig: 20200325_142302[1].jpg -
|