|
Hi,
I've now installed two identical USB Dot Matrix printers, 40 colum wide. One is loaded with sticky labels, the other with a paper roll (for till receipts) They show themselves as 'Generic DMP on USB001' and 'Generic DMP on USB002'
This was determined (I assume) by the following order they were plugged in in the first place. Sofar, when I unplugged and re-plugged, the designations remained the same (on my Test Setup) How confident can I be that this correllation will not be corrupted in future.
As far as the user is concerned, printing happens 'automatically', and on the correct printer. (associations are bound with a setup type program).
The fact that it can distinguish two identical devices at all suggests that the system can read distinguishing features on them.
Does anybody know how the system distinguishes USB items that way.
Regards,
Bram van Kampen
|
|
|
|
|
Bram van Kampen wrote: Does anybody know how the system distinguishes USB items that way.
When you connect your USB printer to the USB bus... Windows is internally requesting information about the device using the DeviceIoControl Function.[^] The IOCTL_USB_GET_DESCRIPTOR_FROM_NODE_CONNECTION[^] control code will return data containing USB_DEVICE_DESCRIPTOR.[^] This struct contains information about what type of device it is Et cetera... Windows saves this data into the registry and associates the serial number with various entries in the registry which represent installed device objects. In theory the serial number should be unique and would remain associated with the printer name you see in usermode.
Hope this helps.
Best Wishes,
-David Delaune
|
|
|
|
|
Thanks, the SerialNumber member seems a candidate to resolve this issue.
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
Bram van Kampen
|
|
|
|
|
I'm completely stumped by this, and I suspect it's a hardware problem. I've got a 1.2 Ghz machine with 512Mb of memory that I've been running Win2K Server on for many years. I decided to reformat and install XP SP2 from scratch. The reformat worked, the initial files copy worked, but when it goes to do the initial boot it hangs. I tried F8 and booting into a command window and it hangs right away. The little progress bar at the bottom of the console screen zips across until it's a solid bar, and then the system hangs there forever.
I've tried this twice now, reformatting from scratch and installing XP. I've also made a boot floppy and it does the same thing, as soon as it tries to access the HD. The only other H/W in the system is a floppy, DVD drive, and a generic VGA card. The mobo has network, soundcard, USB etc.
Any suggestions on how to what to try next? Maybe a different HD? Is my RAM suspect?
[Update] I tried installing Win2K Server just now and it works just fine, as I expected. So now I have a dual-boot system: a good Win2K and a busted XP. Again, I suspect a hardware incompatability, which is why I posted here and not in the O/S forum. [/Update]
Thanks, Dave
QRZ? de WAØTTN
modified on Thursday, October 23, 2008 9:03 PM
|
|
|
|
|
Sounds to me like a driverissue. XP and server2k aren't identical after all.
What storagecontroller does the mobo have?
If it's non standard you should install the manufacturers drivers from a floppy during install (press F6 after core has loaded)
|
|
|
|
|
Thanks for the suggestion Jörgen. I checked around for drivers (Elitegroup 848P-A) and there don't seem to be any updates for the HD controller, other than for the CD. That one is 2.8 Mb, which is too big to put on a floppy anyway.
I think this is a lost cause. I know what you mean about these O/S transitions. I tried to upgrade a Win98 laptop to NT a long time ago and had a similar experience. What surprises me is that I've found that XP seems to be much more forgiving than NT and Win2k ever were. I guess I'll just leave this machine at status quo.  But on the upside, it still runs Win2K exceedingly well 
QRZ? de WAØTTN
|
|
|
|
|
It might be the old classic IRQ conflict.
Disable all devices you don't need, such as audio, lan, modem and firewire (or reenable one). This will give the remaining devices a new IRQ, eventually nonshared, which might allow you to install.
If the installation succeeds you can reenable them later if necessary.
|
|
|
|
|
It's a bit of a pain, but you can slipstream additional drivers/patches into a copy of an OS install CD.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
NetDave wrote: Any suggestions on how to what to try next? Maybe a different HD? Is my RAM suspect?
I take it that the system worked before your reformat.
Some harddrives object to being re-formatted, it is unlikely to be RAM.
Any failing Diskdrive may make the others inaccessible.
To check the HardDrive,
1. Check your BIOS settings, ensure that drives A and C (and your CD Drive) are bootable!
2. Disconnect the harddrive and the CD Rom,(Power and Ribbon Connections, but note how they go back) and run DOS 3.00 from a (bootable)floppy.
If it does not boot, try the floppy on a known system, else, change the floppy drive.this should establish that your hardware is workable.
3. Re-connect the harddrive, and try DOS 3.00 again. If it fails, your Harddrive is dinky.
4. Buy a new Harddrive, and try again. HardDrives are cheap these days.
and do the same.
Hope this is helpfull
Bram van Kampen
|
|
|
|
|
I just tried to install one this morning, and tried to set it up just for wireless, i.e. no ADSL routing etc. The setup wizard seems to insist on going through all that first.
While I can see the 'control panel' using the 168.162.0.1192.168.0.1 address, I can't see the "Wireless Settings" button I'm supposed to click, and a nearby Vista laptop I can't see any wireless networks.
Am I doing something wrong?
Last modified: 4hrs 39mins after originally posted --
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
I've seen that happen with some routers' wizards when you try to skip the dsl-settings: They ignore settings if they deem the wizard "incomplete" - and don't necessarily give you notice. The NetGear support might be able to help you out (IIRC, you're in sort of a hurry).
However stupid that sounds, does the box have one or more antennae? The models all look the same (except for the antennae), so a non-wireless model might have slipped through. Also, the box might have the wrong firmware. Try to upgrade the firmware to the most recent revision.
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
Sebastian Schneider wrote: However stupid that sounds, does the box have one or more antennae? The models all look the same (except for the antennae), so a non-wireless model might have slipped through. Also, the box might have the wrong firmware. Try to upgrade the firmware to the most recent revision.
Doesn't sound stupid at all - it would have crossed my mind if it didn't have an antenna, and a wireless LED flashing on the front panel, that I had got just a DSL router in a wireless box.
Maybe I've got a plain ADSL router firmware in a wireless device? 
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
Sebastian Schneider wrote: However stupid that sounds, does the box have one or more antennae? The models all look the same (except for the antennae), so a non-wireless model might have slipped through. Also, the box might have the wrong firmware. Try to upgrade the firmware to the most recent revision.
Haha, this is closer to correct than we would have suspected. Since I was last there, he has changed his ADSL modem/router to an ethernet only NetGear, with the same IP! I was connecting to his existing one, and not the new one!
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
Earlier this month I was considering buying a NetGear router, not necessarily the WGR614, and am interested in your experiences. However, occasionally, my existing router sometimes allocates a 169... address to a particular PC on my network (doesn't happen nearly as often since replacing ZoneAlarm firewall with Comodo) - the other PC's are correctly allocated a 192.168.1.x address - usually a PC reboot resolves that problem. I have never experienced a 168.162.x.x address and the on-line NetGear manual doesn't appear to cover that specific IP address problem but does suggest you reset the router to factory default. Keep us posted on your resolution of the problem, and, if you so feel, keep us posted on your continuing experiences.
modified 1-Aug-19 21:02pm.
|
|
|
|
|
See my second reply to Sebastian. I had the addresses in my post wrong, and have now edited them.
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
I just realized something weird
Both IP addresses are assigned to Sunguard availability services in the USA.
They are not in any private IP range that I have ever heard of.
Maybe, just maybe, did you mean to connect to 192.168.1.1 or 192.168.0.1 ?
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
Yes, fixed. 
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
Hi, I just install the driver for my new printer HP 2015d and HP PhotoSmart C5280. Everything is working fine but every time that I start up my computer, I found the message indicate that: hppusg.exe Application has generated an exception that could not handled. Process id=0x1270 (4720), Thread id=0x141c (5148). Does any one know what is the cause of the problem? And what is the solution disable this message box?
Thank in advance!
|
|
|
|
|
The problem is that HP can't code its way out of a wet paperbag.
Fixes:
1) if you haven't done so visit HPs website and make sure you have the latest version of their suckware.
2) If that doesn't work (or if you just want to be rid of the suckware in general) start-run-msconfig, startup tab, find the row for hppusg.exe and disable it from starting at boot time. Click apply. It shouldn't try and start the next time you reboot.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
dan neely wrote: 2) If that doesn't work (or if you just want to be rid of the suckware in general) start-run-msconfig, startup tab, find the row for hppusg.exe and disable it from starting at boot time. Click apply. It shouldn't try and start the next time you reboot.
Thank you very much for your help, If i disabled the hppusg.exe from the msconfig dialog box, does it affect any operation of my printer or the software that work with my printer? Thank.
|
|
|
|
|
No more than it crashing every time it tries (and fails) to start already is.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
Hi,
I have a C code that calls an assembly procedure with a parameter that is a pointer to a structure.
typedef struct _SOMESTRUCT {
ULONG arg1;
CHAR arg2[10];
} SOMESTRUCT, *PSOMESTRUCT;
Then in C code, im calling an assembly proc like this:
SOMESTRUCT mySomeStruct;
ret = AssemblyFunction(&mySomeStruct);
In assembly code, how can i access arg1 and arg2?
Any idea?
|
|
|
|
|
arg1 will be the first N bytes of the struct (n = ulong's size in bytes = 4???) arg2 will be the 10 bytes at the address of the struct + N.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
Here is an example of how to access your struct members utilizing inline assembly. This example will copy a string into the arg2 member of your struct.
typedef struct _SOMESTRUCT
{
ULONG arg1;
CHAR arg2[10];
} SOMESTRUCT, *PSOMESTRUCT;
CHAR szcpy[] = "copy me copy me copy me copy me";
_SOMESTRUCT mySomeStruct = {0};
mySomeStruct.arg1 = strlen(szcpy);
__asm
{
lea ebx, mySomeStruct
mov ecx, [ebx]mySomeStruct.arg1
lea edi, [ebx]mySomeStruct.arg2
lea esi, szcpy
shr ecx,1
rep movsw
adc ecx,ecx
rep movsb
}
Best Wishes,
-David Delaune
|
|
|
|
|
How can i check in Run Time if in current machine that execute my application (exe file) has an active microphone ?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
