| Author |
 Topic  |
|
|
eavedesian
8 Posts |
 Posted - 12/10/2007 : 21:58:22
|
I'm having trouble connecting to a windows 98se computer.
It says Hardware error or not connected.
In the driver details in the device manager it says:
"The NTKERN.VXD device loader(s)for this device could not load the device driver. (Code 2.)"
I've read the microsoft tech bulliten with no help. I did not have the NTKERN.VXD extracted from the zip files so I extracted them to the windows/system folder as well as vflatd.vxd & vdd.vxd.
Anyone else have this problem? I've tried to uninstall the software and remove the device from safe mode and try to reinstall but nothing worked. |
|
| Reply #1
nysom
USA
4 Posts |
Posted - 04/06/2008 : 08:14:19
|
| I am getting the same error in 98se. Did you ever find a solution to the problem? |
 |
|
| Reply #2
ZLM
2945 Posts |
|
| Reply #3
nysom
USA
4 Posts |
Posted - 04/08/2008 : 06:56:48
|
The 26.8kb ezusb.sys solves the diver problem but there is a timing
problem when detecting the hardware. Working with John via email on
this now. The 2.08 beta works much better at detecting the hardware
but still loads the wrong driver on install. |
|
|
| Reply #4
ZLM
2945 Posts |
|
| Reply #5
Six_Shooter
11 Posts |
Posted - 05/02/2008 : 19:18:19
|
quote:
Originally posted by ZLM
The latest software shouold solve both driver and communicaiton issue in Win98SE.
Here is the beta version:
http://www.mcumall.com/download/TrueUSBWillem/TrueUSBWillem2.08BetaSetup.exe
I have found an issue, or possible issue that occured tonight when I was trying the beta software.
I was attempting to place a 4K at address 0000, and it would be placed at 8000, I tried several times to place it at 0000, filled buffer with FF, closed the software, re-opened the software, always placed at 8000. I also noticed when this was happening the previous 4K bin file that was placed at F000, was still shown in the buffer.
I went back to 2.07 and was able to once again, place the bin file at 0000. |
|
|
| Reply #6
ZLM
2945 Posts |
Posted - 05/03/2008 : 00:20:51
|
The .bin file should always loaded from 00000. Unless you set the file offset.
|
|
|
| Reply #7
Six_Shooter
11 Posts |
Posted - 05/03/2008 : 05:21:12
|
quote:
Originally posted by ZLM
The .bin file should always loaded from 00000. Unless you set the file offset.
I understand that, what I'm saying is, I experianced a problem with the 2.08beta software, with the offset set 000000, checked that several times. |
|
|
| Reply #8
ZLM
2945 Posts |
Posted - 05/03/2008 : 08:17:13
|
Tested again and did not find anything wrong. Would you pelase list the exact steps to reproduce the problem?
If we could not reproduce the bug, then we can not fix it.
|
|
|
| Reply #9
Six_Shooter
11 Posts |
Posted - 05/03/2008 : 11:53:07
|
Click on "open"
browse to 4K bin, double click on it.
That's all I did, no extra steps, just tried to open like normal.
Re-installed 2.07 and problem went away. |
|
|
| Reply #10
ZLM
2945 Posts |
Posted - 05/04/2008 : 07:59:10
|
Tested again, it still works fine on 2.08Bata.
Steps:
1. Connect the programmer.
2. Run the software.
3. Select a device. eg. SST27SF512
4. Confirm the File Offset value is 00000 OR 0
5. Open a binary file.
Then the bin file data is loaded correctly in the buffer from address 00000. |
|
|
| Reply #11
Six_Shooter
11 Posts |
Posted - 05/04/2008 : 08:28:49
|
quote:
Originally posted by ZLM
Tested again, it still works fine on 2.08Bata.
Steps:
1. Connect the programmer.
2. Run the software.
3. Select a device. eg. SST27SF512
4. Confirm the File Offset value is 00000 OR 0
5. Open a binary file.
Then the bin file data is loaded correctly in the buffer from address 00000.
I did exactly that, and I'm letting you know that I experianced a problem, just as an FYI. |
|
|
| |
Topic |
|
Won't communicate on windows 98se
