MCUmall EPROM BIOS Chip Burner Forum
MCUmall EPROM BIOS Chip Burner Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ
Save Password
Forgot your Password?

 All Forums
 MCUmall Forums
 TOP USB Programmer
 EAccess Violation Problem solved!

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List Spell Checker

* Forum Code is ON
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

   Insert an Image File
Check here to include your profile signature.

T O P I C    R E V I E W
leutholl Posted - 11/16/2005 : 02:12:03

I just solved this bloody EAccess Violation problem. Now my TOP2004 programmer works perfectly and I can start it as much as I want.

The problem was - well, let's say - very easy.

Everytime the TopWinEn (I think TopWin too) closes, it writes a file "top2004.cfg" in the program directory. There are some configuration paramters stored in plaintext but realy is not important!
Somehow, the program has a Extended Access Violation exception if this file is existig during startup. It has nothing to do with the USB driver or the device. If you have both drivers (WinDriver for the Jungo USB API used for USB Support in Windows User Mode and TOP Programmer driver which Windows installs because it sees the USB device) working with no yellow explanation mark in the control panel trust the program it will manage USB well.

So, the solution is simple, just delete this cfg-file before you start the program. It works perfectly!

Another thing I found out is this "Reload USB driver"-Tool. It simply starts a new process called wdreg.exe (see it in the task manager). Watch out that you only have one instance of this process in the task manager. If you start the tool again it installs another instance of this process.

On my system once the drivers as descriped above are working - I don't need the wdreg.exe running. As the name tells, I think it has something to do this registration of a windows driver. Maybe only in the registry - I don't know exactly.

So I'm happy to have this unit working and I hope it will enjoy me in future writing and reading to EPROMs.

I hope this issue is now solved for everyone. I would like to hear from you if you can fix the problem.

Greetings from Switzerland,

Lukas Leuthold
2   L A T E S T    R E P L I E S    (Newest First)
pokernut Posted - 02/03/2006 : 17:48:01
Thanks so much for the info on that EAcces Violation. It worked great for about 4 programmings and then it just died. This thing is so tempermental. After 8 more restarts I got to work for 6 more chips. Any other secrets you have about keeping this thing working would be gratly appreciated
usb Posted - 11/18/2005 : 01:30:12
Thank you very much for your information. I had this problem on one computer and I did not know how to fix it. Now I can try your method.

MCUmall EPROM BIOS Chip Burner Forum © Copyright 2003 - 2009 Mcumall Electronics Inc. Go To Top Of Page
Generated in 0.08 sec. Snitz Forums 2000