KMFM$

Well, it is a network printer, sort of. The printer (device) is connected to a machine (A) and there are other clients that access it (B ). Then there is a program which multiple people use ©. So the print device is connected to (A), which is where it is being shared from, on LPT1 on that machine. Other systems have devices on LPT1 so by using "NET USE LPT1 \\COMPUTER\PRINTER" is out of the question. Unfortunately, the program cannot use an IP address for the print device. The only options are COM1, COM2, LPT1, and LPT2 (VERY limited program, I know). So, for the clients (B ) to properly access the shared printer off of the host machine (A), I had NET USE LPT2 \\COMPUTER\PRINTER /PERSISTENT:YES, which would send the print job to the properly configured LPT2 port for the appropriate print device. Again, other machines have different COMs and LPT1 port(s) in use, so I couldn't think of another way. One error I was receiving, though, was the "Local Downlevel Document" job sporadically loading and unloading in the device print queue. Therefore, I am thinking that this was from someone sending a job to the printer while the printer was still configuring itself. I am going to NET USE LPT1 /DELETE and reinstall the printer on the host machine and see if that helps the situation.

So, a new employee needed to have a local port mapped to a network printer. For everyone else's system, during the initial install, I used: net use lpt1 \\computer\printer /persistent:yes No problems there. So now I come to find out that someone changed the port in the program, unknowingly (so he says). Anyway, after this change they changed the port of the printers. Now, I fear that when ran the net use command I overwrote the printer port configuration. Now, when trying to access the default printer (which would have been overwritten by the net use command), all I receive are streams of "Local Downlevel Documents" in the queue. Now no one can print from the default printer. I am assuming that there are jobs sent from out on the network that are causing this error, but I really have no clue. Any help would be appreciated. BTW- running net use lpt1 \\computer\printer /persistent:YES for the default has no effect locally or across the network. I have also closed all sessions then reinstalled the printer with updated drivers to no avail. I am afraid that the more I try the deeper the hole gets.

Hey, ripken, if you're still looking for a module to read net traffic try xlabel and detect-1.0-beta_5. IIRC, detect can pull that info.

Clean Desktop Dirty Desktop I'll post what I'm using in a little bit.

I actually like to use existing .logonxp themes. I just pull the graphics and the UIFILE out of the .logonxp theme via ResHack and put them into my logonui.exe's via ResHack too. Works like a charm.

I don't know if you can do that from [DiskConfig] or not. I have never come across anything like that in my searches. I have managed to do it, but I used the WinPE method. I created a DVD and created so that it boots in to PE, runs a diskpart / format script, then proceeds to the install. It is all automated, but you said you don't want to use WinPE. Sorry I can't be of more help.

Quick question. Does anyone know of any way to skin the bar? I already have the uxtheme.dll patched and my current VS isn't applied to it. Don't know if it's possible, just thought I'd ask. B)

Wow. This is Directory Opus? Whew. I'll agree with some of the other guys, Directory Opus is probably the best file manager out there. I have used it even before it was callled Directory Opus. It was named PC Opus then, and still just as amazing. The choice of colors for this is apparantly a single-sided perception, but the underlying file manager is astounding. Give it a try before running away because of this screenshot.

I knew about the first tip for quite a while (god knows how many years). However, the second is news to me (also a great tip to know).

Did you mod the shellstyle or did you find it somewhere? I've been searching to get the information pane (the left pane in your explorer window) to look as you have yours, but I can't find anything on it. I could definitely do the mod, I just need to know where to get started. Any help would be appreciated.

Thanks. I've figured it all out now.

I figure this is the best section for my question, since I am trying to install a program. Does anyone know if long file names are supported in Windows inf's. I know that the 9x systems do not support it, but I only plan on using this on NT-2k3 systems. I have googled and googled (though I wouldn't doubt that I've been googling the wrong terms), but cannot find a straight answer. Mainly I am wondering about the [sourceDisksFiles] section and the ability to have things such as: [SourceDiskFiles] Grim Fandango.exe = 1 My First.exe = 1 Those, of course, are only examples. Just curious to what, if any, kind of usage characters I need to use (e.g.- " _ ' -) Thanks for any assistance that can be provided.

I know that I just add my bootskin.cmd to run at around T-10 with cmdlines.txt. That way, the reboot that is automatically performed after the GUI mode finishes will take care of it. So after my machine comes up, it has the new bootscreen loaded. Hope this helps.

Has anyone looked into hacking shell32.exe (the WM2003 shell) to disable or make the separator lines on the Today Screen transparent??? I have not been able to move shell32 anywhere to look at it. I'm not sure if it's because the .exe is in use or something else. Copies to a memory card fail with no warning and the file cannot be seen from XP file explorer. I'm sure I could do a ROM dump, but I have no clue where to go with that... If anyone has ideas, please post them.

I'd say go for the Axim x50v. I own a HP iPAQ 2215, which is similar to the h5550/h5555 that you have listed. They are good PDA's but the technology is slowly starting to lag. Mine (and I believe the h5555) has a 400MHz Xscale with a 200MHz FSB, and I can do just about anything on it (I use Pocket Hack Master 2004 to "properly" scale the Xscale Proc. I have "safely" overclocked it to 572MHz with a 148MHz memory frequency and ~250MHz FSB. I could go higher, but I don't want to ruin my PDA and I don't have any real use for the extra power.). The iPAQ's you listed run Windows Mobile 2003, while the Axim uses Windows Mobile 2003 Second Edition and will probably be upgradable [sic?] to Windows Mobile 2005 (aka- Magneto). Also, if you want to use your PDA for "graphics intensive" games, I would recommend the Axim for the fact that it has 16MB dedicated graphics memory (if I remember correctly). I have been looking at upgrading my PDA, and have been looking at the Axim x50v quite seriously. Also, the Axim has a "True" (notice the quotes. ) VGA display while the iPAQ's (at least the h5550's. The hx4705 has a VGA display as well) use QVGA. Of course, as usual it's up to want you to use your PDA for and how long you plan to keep it. I can't comment on any of the others, because I haven't used those. Hope this helps.