Mark this thread as Unsold
MB Star Diagnosis for Sale
11-12-2017, 10:26 AM
#1
Member
Thread Starter
MB Star Diagnosis for Sale -SOLD
For sale is STAR DAS - diagnostics computer. I no longer have need for this as im selling both my cars.
$450 Shipped. Works through 2015 Models.
Thanks!
$450 Shipped. Works through 2015 Models.
Thanks!
Last edited by kmancoupe230; 11-18-2017 at 05:52 PM.
The following users liked this post:
Richrpilot (11-23-2017)
Trending Topics
12-04-2017, 01:06 PM
#9
Member
Join Date: Mar 2011
Location: Southern California - Temecula
Posts: 206
Likes: 0
Received 2 Likes
on
2 Posts
2005 E55 AMG Estate
If anyone needs one, I have full C4 developer mode in VMware Virtual Machine that I was able to program. All you need is buy any C3 C4 Multiplex on ebay and a usb rs232 cable and you can run this on any computer or laptop. You don't need a bulky old Dell laptop. I run this on my Windows 10 pro Surface Pro 4, and my Lenovo Yoga. I can even have it run on MacOS, if you have VMware Fusion. The current one i have is up to date to 2014 models.
I can give you link to download the software and full STAR Xentry, and when booted it will need to activate again because it will detect a new machine ID.
PM, price is much cheaper than buy a full unit with laptop. Bascially just a bit of my time and you find whatever Multiplex.
I can give you link to download the software and full STAR Xentry, and when booted it will need to activate again because it will detect a new machine ID.
PM, price is much cheaper than buy a full unit with laptop. Bascially just a bit of my time and you find whatever Multiplex.
12-09-2017, 10:09 AM
#10
MBWorld Fanatic!
What do you mean by full developer mode?
And what you're saying is that the lap top is booting a virtual machine and the drivers for the multiplexer have to work too. Because it's a c4 I would think that a cat5 cable should work but you're saying that the serial cable is still needed.
Last time I bought an external hard drive and the rs232 cable. Then bought a lap top, transferred the info and installed the virtual machine on the native hard drive then installed the xentry and drivers.
Booting a large virtual machine takes an incredible amount of time and resources. By the time I got a solid state hard drive and maxed the ram of the lap top, it finally booted it in about 3 minutes.
Then the problems begin
The drivers from inside the virtual machine have to connect to hardware resources of the lap top. There is a allocation table I buried deep in there.
There are theories and schools of thought of what should be done with those.
Then basically the lap top never managed to properly allocate the serial port it had to the cable to the mux.
Not even when the tech guy took a troubleshooting session via go to meeting.
Then I tried using a serial to usb converter.
Connect to the mux without using a serial port on the lap top.
But then the software and driver for the converter have to be installed inside the virtual machine and properly allocated.
Did not happen.
You solved all of this, right ?
And what you're saying is that the lap top is booting a virtual machine and the drivers for the multiplexer have to work too. Because it's a c4 I would think that a cat5 cable should work but you're saying that the serial cable is still needed.
Last time I bought an external hard drive and the rs232 cable. Then bought a lap top, transferred the info and installed the virtual machine on the native hard drive then installed the xentry and drivers.
Booting a large virtual machine takes an incredible amount of time and resources. By the time I got a solid state hard drive and maxed the ram of the lap top, it finally booted it in about 3 minutes.
Then the problems begin
The drivers from inside the virtual machine have to connect to hardware resources of the lap top. There is a allocation table I buried deep in there.
There are theories and schools of thought of what should be done with those.
Then basically the lap top never managed to properly allocate the serial port it had to the cable to the mux.
Not even when the tech guy took a troubleshooting session via go to meeting.
Then I tried using a serial to usb converter.
Connect to the mux without using a serial port on the lap top.
But then the software and driver for the converter have to be installed inside the virtual machine and properly allocated.
Did not happen.
You solved all of this, right ?
Last edited by Vladds; 12-09-2017 at 10:19 AM.
12-28-2017, 02:14 PM
#11
Member
Join Date: Mar 2011
Location: Southern California - Temecula
Posts: 206
Likes: 0
Received 2 Likes
on
2 Posts
2005 E55 AMG Estate
What do you mean by full developer mode?
And what you're saying is that the lap top is booting a virtual machine and the drivers for the multiplexer have to work too. Because it's a c4 I would think that a cat5 cable should work but you're saying that the serial cable is still needed.
Last time I bought an external hard drive and the rs232 cable. Then bought a lap top, transferred the info and installed the virtual machine on the native hard drive then installed the xentry and drivers.
Booting a large virtual machine takes an incredible amount of time and resources. By the time I got a solid state hard drive and maxed the ram of the lap top, it finally booted it in about 3 minutes.
Then the problems begin
The drivers from inside the virtual machine have to connect to hardware resources of the lap top. There is a allocation table I buried deep in there.
There are theories and schools of thought of what should be done with those.
Then basically the lap top never managed to properly allocate the serial port it had to the cable to the mux.
Not even when the tech guy took a troubleshooting session via go to meeting.
Then I tried using a serial to usb converter.
Connect to the mux without using a serial port on the lap top.
But then the software and driver for the converter have to be installed inside the virtual machine and properly allocated.
Did not happen.
You solved all of this, right ?
And what you're saying is that the lap top is booting a virtual machine and the drivers for the multiplexer have to work too. Because it's a c4 I would think that a cat5 cable should work but you're saying that the serial cable is still needed.
Last time I bought an external hard drive and the rs232 cable. Then bought a lap top, transferred the info and installed the virtual machine on the native hard drive then installed the xentry and drivers.
Booting a large virtual machine takes an incredible amount of time and resources. By the time I got a solid state hard drive and maxed the ram of the lap top, it finally booted it in about 3 minutes.
Then the problems begin
The drivers from inside the virtual machine have to connect to hardware resources of the lap top. There is a allocation table I buried deep in there.
There are theories and schools of thought of what should be done with those.
Then basically the lap top never managed to properly allocate the serial port it had to the cable to the mux.
Not even when the tech guy took a troubleshooting session via go to meeting.
Then I tried using a serial to usb converter.
Connect to the mux without using a serial port on the lap top.
But then the software and driver for the converter have to be installed inside the virtual machine and properly allocated.
Did not happen.
You solved all of this, right ?
