|
ForNow wrote: only for Windwos CE not XP correct?
Yes
|
|
|
|
|
I know you you are the one who told me this thankx
How about I start a Kernel mode thread PsThreadCreate... maybe to do my Kernel mode work
whitout wasting your time is there anyway I can do Kernel mode type work in user mode
or should I forgot this
|
|
|
|
|
ForNow wrote: How about I start a Kernel mode thread PsThreadCreate... maybe to do my Kernel mode work
PsCreateSystemThread can only be called from kernel mode so it won't help you in user mode.
ForNow wrote: whitout wasting your time is there anyway I can do Kernel mode type work in user mode
No you can't. That's why one is called kernel and one is called user - they are very distinct and only communicate through a few well-defined interfaces.
Judy
|
|
|
|
|
|
Hi,
I am using Stackwalk to go from the DLL_THREAD_ATTACH current thread to the originating thread
There is an APC type function KiUserAPcDisptach that messes up the stack Frame
does anyone know if APC type call saves the current stack Frame somewhere maybe a context pointer
thankx
|
|
|
|
|
Hi,
I am getting the following error 0xC0000005: Access Violation., is there is a reason why I am getting, my code compiles correctly but while debugging i am getting this error.
here i am getting the error
CTagList *pObj= (CTagList *)lstTagInfo.GetNext(pos);
With Regard
Mytheensha
|
|
|
|
|
sorry i wrongly post here
With Regard
Mytheensha
|
|
|
|
|
Hi,
As a concept, I would like to write a kernel driver just to read kernel structure data and send the information back to a user mode application (in Windows XP). I have absolutely no experience doing this kind of thing, and, in all honesty, it scares the hell out of me. I have read much of the available literature (Windows Internals, and the documentation that comes with the Microsoft DDK), but, the kernel is a murky, nebulous region of the cosmos, and I am extremely reluctant to invade it without, say, a God-like sense of comprehension.
Initially, my appraoch is to use the source examples provided with the DDK, but, I'm wondering if testing something like that can destroy or damage my operating system, or the device drivers currently residing there. If this is an evolutionary process, I don't want to become bytestream roadkill.
Any good suggestions from those of you have survived the development process, besides reading the forum posts at OSR and Sysinternals?
|
|
|
|
|
Baltoro wrote: Initially, my appraoch is to use the source examples provided with the DDK, but, I'm wondering if testing something like that can destroy or damage my operating system, or the device drivers currently residing there.
Yes, in fact when I first started developing device drivers I was locked out of my operating system several times. It was quite embarrassing. I would highly recommend testing your device drivers in VMWare or VirtualPC. It is extremely easy to create a race condition in device drivers. It can be a challenge to repair the OS when a faulty driver is installed. Once I had to edit the registry from a boot CD to prevent an upper level filter driver from attaching. No more driver development outside of VMWare for me! I have since learned my lesson! 
There are additional benefits to running your test drivers in a virtual environment. It makes debugging the driver much easier. There is a gentleman named Dana Epp[^] who has a site dedicated to those seeking ring-0[^]. He has written a tutorial showing how to use WinDbg with VMWare[^].
I have found the following blogs to sometimes contain useful information:
A Hole In My Head[^]
Pointless Blathering[^]
It Goes To Eleven[^]
OSR online[^] is also a great resource. There are many knowledgeable engineers there who are willing to help out. I would highly recommend joining the discussion lists. See you there!
Best Wishes,
-David Delaune
|
|
|
|
|
David Delaune,
Thank you very much for the excellent suggestions, that is exactly the type of information I was looking for, but, was completely oblivious to.
|
|
|
|
|
Baltoro wrote: I'm wondering if testing something like that can destroy or damage my operating system
Oh yes!
Baltoro wrote: or the device drivers currently residing there
Deffinitely!
Baltoro wrote: If this is an evolutionary process
And about as slow. But more painfull.
Baltoro wrote: Any good suggestions
1) Ghost your system. You are going to need it.
2) Never set a test driver to auto start. You can get into a boot-bsod-boot-bsod loop.
3) Get Walter Oneys book.
4) Use a DDK sample to start with. Say, a simple IO, or a write to buffer/read from same buffer driver to het a feel if you like.
I have spent about 10 years writing drivers, still learning stuff!
Morality is indistinguishable from social proscription
|
|
|
|
|
fat_boy,
Thanks, I was worried about actually loading and executing, and the potential for irrevocably damaging essential components.
Now, I know,...
Thanks again, I really appreciate it.
|
|
|
|
|
Hey guys,
I'm developing an application that a user can design and print labels for CDs and DVDs. I'm wanting to add the functionality to print directly on the disk if the printer has the capability. The question is: How do I find out if the printer can do direct disk printing? The .Net framework doesn't seem to provide an interface for interacting with such printers. I have wrote a number of manufactures asking for advice but they didn't seem interested in talking to me when they found out I wasn't apart of some big company. Can you pros here a CP help me? 
Cheers,
Richard
If you could rent a programmer a hour and a half for a dollar and a half, how much would he charge for 10 hours?
|
|
|
|
|
Certain windows OS'es such as Vista and Windows Server 2003 with SP1 can create partitions more than 2TB in size using GPT. Suppose I have such machine with single partition spanning 3TB in size under drive letter D. Would a regular windows XP 32bit machine (which do not support GPT by the way) have any problems connecting to that partition when mapped to \\machinename\D$? Any issues when reading or writing data?
Anybody has experience doing something like this?
Thanks.
|
|
|
|
|
The SMB protocol used by Windows file sharing doesn't deal in disk offsets. It asks the server to open the file for it, passing the filename to get a handle. The fact that D$ is the root of the filesystem is irrelevant.
The SMB protocol supports 64-bit offsets for read and write operations, so you can manipulate very large files (> 4GB).
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
I'm not sure you understood the issue, either that or I'm not seeing definitive answer to my question in your reply.
See this link:
http://www.carltonbale.com/2007/05/how-to-break-the-2tb-2-terabyte-file-system-limit/
Most of the older windows operating systems (including windows xp 32 bit) only support MBR partitioning meaning they cannot create or work with partitions more than 2TB in volume. To get around this problem Microsoft introduced GPT partitioning in latest operating systems. With GPT there are virtually no limits on the partition size.
The problem here is not connecting to the drive root or working with files >4GB. It's whether the system that does not support GPT such as windows xp 32bit can connect to a network share >2TB in size and work correctly with it.
I would hope that network protocol would abstract it all away. However, I have read reports that xp had problems writing to linux (yes, I know, slightly different) network share that was 3TB in size. So I wanted to ask if anyone knows if that really is a problem or not.
|
|
|
|
|
I am building an x64 kernel mode driver with WDK 6000. Two intrinsics are used: __readmsr and __writemsr.
As mentioned in MSDN Library, it requires to include <intrin.h>. But there is no such file in the inc folder and the subfolders of WDK 6000!
What is the correct include file for these intrinsic functions? Thanks!
Maxwell Chen
|
|
|
|
|
The intrinsic functions are a compiler feature, not a WDK feature. Look in the compiler Include tree. For example, C:\Program Files\Microsoft Visual Studio 8\VC\include.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
I bought a fanless Via-based system with 256 mb RAM from eWayCo and have been trying to get it to boot Win XP, which it claims it should be capable of (not just the embedded version). The machine has no floppy drive or cd drive, just an IDE slot.
Using an IDE-CF adapter on another computer, I was able to install XP to the CF card, disable virtual memory and install all the XP updates.
Plugging the adapter into the fanless system, I can boot and it displays the XP boot menu ("Your computer didn't start correctly last time...") and I choose safe mode. Everything goes fine until it trys and loads gagp30kx.sys, which I understand is a Via video card driver. I modified boot.ini to allow me to boot into VGA mode, which just displays a blank screen.
I know this is a long shot, but any ideas on how I might be able to get this thing to boot?
Thanks!
modified 12-Jul-20 21:01pm.
|
|
|
|
|
We recently went through this with a (VIA) Jetway ITX board.
Try installing the operating syatem from an external USB CD drive.
You may have to make changes to the BIOS settings to get the system to boot from the CD.
|
|
|
|
|
I've tried this with a couple of USB CD drives, and I was unable to get the device to be recognized so that I could off of it. Do you know of any boot environment, like the old windows boot disks with CD support, that I could use to load drivers for the cd driver to start the installation?
edit: this would have to boot off a flash drive
modified 12-Jul-20 21:01pm.
|
|
|
|
|
The motherboard's bios should support booting from a CD. The windows XP installation CD is bootable.
On our machine we did have problems with the factory BIOS settings. The system would not boot from a USB CD. I finally solved this problem by enabling all appropriate USB options.
Another possibility is to attach the required hardware (CD, Floppy, etc.) directly to the motherboard.
|
|
|
|
|
There is a site "bootdisk.com" or "bootdisc.com" that has tons of bootable images.
|
|
|
|
|
I ended up getting this working by making a flash drive a bootable XP install.
Thanks for the suggestions
modified 12-Jul-20 21:01pm.
|
|
|
|
|
You should install on the hardware the box needs. Just install to a normal harddisk on the fanless system, then use another comp to pull an image and write that to the CF-card.
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
