|
TIMDLL from http://codeproject.com/ccp/JpmTimers.asp
or
BOSDLL from http://codeproject.com/ccp/BOS.asp
had just this in mind.
Both use a MultiMedia timer, it trips a heart-beating thread (every millisecond) which: -
1) spins-a-thread(starting at user supplied entry point),
2) causes a function execution(starting at user supplied entry point) or
3) sets an event-flag
as the user has specified. It is accurate to one millisecond.
Lymington
|
|
|
|
|
Thank you Lymington for your reply. I am currently trying to understand your code.
Yours
S.Senthlkumar
|
|
|
|
|
Outlook 2000 ( sp3 ) is eating a lot of my CPU time, 99% when doing nothing; no network activity, just running wildly ... on its own ... ?
kinda' puzzled ... at least, it doesn't look it's sending out emails by the tons ...
Thanks for any info ...
Max.
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
This is mostly FYI:
For some time I have been unsuccessfully trying to install Windows 2003 on a Asrock K7S8XE MB / AMD 2400+. Also with the patches (applied April 9th)for windows 2000 this machine would no longer boot with that system either. So I concluded something must have been damaged on the board during some power failures (had several light strikes on the power lines this spring.) even with a line conditioner in the circuit. I was wrong, a new board (new rev of same model) had no impact. I have the same mb on several systems and drives in cradles so I can rearrange the system.
I have finally traced both problems this last weekend to a NEC 100Meg Zip drive. I swapped it out with a second drive and also a Iomega 100 and all had the same impact. Recieved a drive io error message and then the machine would crash and restart. Removed the zip drive and all is well. It also works fine with a 250 meg drive.
So I do not know if this is just a freaky combination or the drive in general. Is anyone using 100meg zip drives with other mb's?
I do not mind getting old. It beats all the other options that can think of.
|
|
|
|
|
I tried using my 100 meg Iomega Zip Drive with my XP machine.
After spending a day at trying to get it to work, I downloaded all the drivers from Iomega, I threw it in the trash. I could not even sell it on eBay.
I have a CDRW now, and I will never use a Zip Drive again.
|
|
|
|
|
I would like to point out it is the 100 that is not ATAPI compatible. The 250 that I have is fine.
I do not mind getting old. It beats all the other options that can think of.
|
|
|
|
|
I'm developing an application that needs to lock the desktop, taskbar, switching keys, ...
I'm hidding the desktop using the following code:
ShowWindow(FindWindow(NULL, "Program Manager"), SW_HIDE);
I'm hidding the taskbar using the following code:
ShowWindow(FindWindow("Shell_TrayWnd", NULL), SW_HIDE);
The problem arrives if the user double click the desktop area - the start menu appears !
I need to disable the mouse clicks in the desktop.
I used the following (hook) code in Win9x:
LRESULT CALLBACK MouseHookProc(int nCode, WORD wParam, DWORD lParam)
{
if (nCode >= 0)
if (wParam == WM_LBUTTONDBLCLK)
if (((MOUSEHOOKSTRUCT *)lParam)->hwnd == GetDesktopWindow())
return 1;
}
return CallNextHookEx(hHook, nCode, wParam, lParam);
}
or
LRESULT CALLBACK GetMessageHookProc(int nCode, WORD wParam, DWORD lParam)
{
MSG *p = (MSG *)lParam;
if(nCode >= 0)
if ((p->hwnd == GetDesktopWindow()) && (p->message == WM_LBUTTONDBLCLK))
p->message = WM_NULL;
return CallNextHookEx(hHook, nCode, wParam, lParam);
}
This works fine in Win9x but doesn't work in Win2K !
If I use the WH_MOUSE_LL in Win2K it works fine !
I would like to use the same code for Win9x and WinNT/2K.
Can anyone help me ?
|
|
|
|
|
I have converted our production server to 2003 Server and
have one website that is giving me fits. I am getting the
following error on a CreateObject("scripting.dictionary")
command. The error is
Server object error 'ASP 0178 : 80070005'
Server.CreateObject Access Error
The call to Server.CreateObject failed while checking
permissions. Access is denied to this object.
I have found and followed the knowledgebase articles that
tell you to make sure IUSR_<servername> has read execute
acces to the msvbvm60.dll and it doesn't correct the
error. If I make IUSR_<servername> and member of the
administrator group it works. I have even tried to get
IUSR_<servername> full access to the C Drive and even that
doesn't work. Only thing that does work is to make the
user part of the Admistrator group and thas leaves a
security problem. Any ideas on how to fix the problem?
Please help
Thanks in advance,
Navneet
|
|
|
|
|
This object is implemented in the scrrun.dll library; you should ensure that the IUSR_ user has read and execute access to the System32 directory (I think).
The full access to C: had no effect, at a guess, because the Windows\System32 folder doesn't inherit its ACL from the parent. I can't test this theory right now because I don't have a Windows Server 2003 system handy.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
I would suggest you right click on your c Drive and go to the security tab. In that see if the windows 2003 administrator is available. Go to the advance tab and see who the owner is. change the owner to the windows 2003 administrator. Add the user to this file in the security tab and give him rights.
Tarakeshwar
CCIE Q(Routing and Switching), MCSE Security
|
|
|
|
|
Hi Friends,
Is there any way to install office 2000 developer on named instance?
VikramS
|
|
|
|
|
Hi boys
any boady knows to lock a file ?
krishnadk
|
|
|
|
|
Hi,
I have an remote Win-XP box to which I need to connect (Means I want to log on to Win-XP box from Win 2000 Prof box) . How can I get connected on to it. I am on a box which has Windows 2000 Professional.
Came to know that Terminal services is not for Win-XP, Will WinVNC work?
Or any other way.
Thanks,
Prashant
|
|
|
|
|
If it's Windows XP Pro, go to Control Panel > System, Remote tab, and check 'Allow Users To Connect Remotely To This Computer'. You can now use Remote Desktop Connection[^] to connect to the PC. Remote Desktop Connection is basically the new name for Terminal Services Client.
XP Home doesn't offer Remote Desktop.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Hi guys
How we can recover a deleted file in windows. i think we can do it by changing some file table entry.
Help me if any one knows.
Thanks in advance
bye
i can do anything
|
|
|
|
|
What do you mean? By any software or by your software?
There are alot of utilities that can help you recovered deleted files. For example: GetDataBack, DiskEdit, iRecover, NU...?
|
|
|
|
|
I have a standard Win32 application ( MFC, SDI ) that I have written.
On most user's desktops, set to run at 1280x1024 with "small fonts", the application appears fine.
However, when the application runs on one user's machine the fonts appear larger than normal causing the application's window to not fit on the display without showing scroll bars.
I have verified her settings are 1280x1024 with "small fonts" like everybody elses ..
What else should I look at to determine why the application is behaving differently on her machine ?
|
|
|
|
|
You'd think something like this would be easy... but it has been a difficult journey so far. But anyway, I am simply trying to be able to run the MSDN installer from the command line, in an unattended mode.
I can mostly make it work with this gem:
msiexec /qb /i F:\msdn.msi SETUP_EXE=yes
(assuming F: is a CD or network share or someplace containing the MSDN install package.) That will always install it into C:\Program Files\MSDN, and I may or may not want it there. I want to be able to specify a target directory on the command line.
After some poking in the MSI package, I tried this, but to no avail:
InstallFolder=C:\Foo
I then found I can specify this property to make it work:
MSDN_QTR.3643236F_FC70_11D3_A536_0090278A1BB8=C:\Foo
There has to be a better way. I am worried that the identifier there is arbitrary and might change on me when the next MSDN comes out. Does anyone know a better or more reliable way of doing this??
Sometimes I feel like I'm a USB printer in a parallel universe.
|
|
|
|
|
Do you have a copy of ORCA or msi2xml?
This would let you look in the tables, and you could examine different MSIs from say, Jan and April, and see if the install folder is different. This will be in the properties table somewhere.
The trailing bit looks suspiciously like a GUID, so it may well change from release to release...
Steve S
|
|
|
|
|
Yes, I found it using ORCA. I should probably look in the April release (I used this one from the January release) to see if it changes... if it does, I guess I'm hosed.
Sometimes I feel like I'm a USB printer in a parallel universe.
|
|
|
|
|
This is odd. The PC I gutted last week, replacing the PII motherboard with a 3GHz P4, runs as slow as the old one. A bit of exploration revealed that the C: drive is operating in MS-DOS Compatibility Mode. That explains the slow operation, but none of the Technet Knowledge Base solutions applies to this unit. I've sorted through about 40 of the articles, and all talk about specific situations which are not applicable. Any other ideas?
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|
|
Roger Wright wrote:
replacing the PII motherboard with a 3GHz P4
I can't say I've ever used a P4 as a motherboard for a PII system...
Seriously though, you might want to check the bios see if there is something in there. (Assuming this was the Win 98 machine you were talking about earlier) Could it be something with some of the P4 features that aren't compatible with 98? Is hyperthreading enabled?
Matt Newman
All rise for the honorable Judge Stone Cold Steve Austin - From Dilbert Episode 30
|
|
|
|
|
Matt Newman wrote:
Could it be something with some of the P4 features that aren't compatible with 98?
I doubt it, as I've seen a few systems using a P4 with Win98SE. Things just got weirder, too. I was working on another Win98SE PC today for an entirely different customer, and that one is running in MS-DOS Compatibility Mode, too! What the heck is going on here, some kind of plague?
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|
|
MS-DOS Compatibility Mode can sometimes be caused by a boot-sector virus. Use a virus scanner.
My other suggestion is to use a modern operating system
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Although searching Technet has been futile, Google came up with some interesting tidbits. For one, if the PCI controller supports serialization between channels, and a CD-ROM driver is loaded from AUTOEXEC/CONFIG, the hard drive is forced to operate on Compatibility Mode. Another is a damaged MBR caused by an earlier virus infection - and I know that both PCs have had virus problems before. A third possibility is that, at some time in the past, the system failed to intialize 32-bit protected mode drivers for the drive controller. Once that happens, a NoIDE value is added to HKLM\System\CurrentControlSet\Services\VxD\IOS, and several entries of BAD_IDE are written in the Registry. If these are manually removed the system will attempt to detect a 32-bit driver again, but as long as they remain it will never try again.
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|