Hi all,
WaxDragon gets this,
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(./lib/advapi32/service/scm.c:2035) dwBufSize: 0
(subsys/system/services/rpcserver.c:1759) ScmrStartServiceW() called
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was cf)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xf000e739 could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65a69 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65d92 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a1f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cb1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00000c33>
kdb:>
I get this,
(lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv'
(Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr
v' (Status c0000135)
(./subsys/win32k/ntuser/class.c:137) Failed to lookup class atom (ClassName 'SHE
LLDLL_DefView')!
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was ec)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xdeadbeef could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65aa9 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65dd2 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a5f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cf1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00003443>
<00000000>
kdb:>
Second reboot it worked after booting linux than reboot warm, third reboot by power on reset,
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was ee)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xdeadbeef could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65aa9 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65dd2 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a5f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cf1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00002eee>
<00000000>
kdb:>
I can repeat this over and over with real hardware,
Thanks,
James
Hey everyone, just a quick question.
Does anyone know of an existing application that will accept a bunch
of header files as input and output a list of function prototypes? It
would really help with my code auditing as I'm spending a long time
assembling them by hand and it takes a long while.
Cheers,
Martin
weiden(a)svn.reactos.org wrote:
> disable starting lsass.exe for now
It seems that rpcrt4.dll has a bug that massively leaks threads in an
rpc server. It seems that it leaks one thread per request.
- Thomas
Hello Ged,
> some new toolbar icons
>
> Updated files:
> trunk/reactos/subsys/system/explorer/res/toolbar.bmp
Please use only toolbar bitmaps with 15 pixels height, not 16 !
Regards,
Martin
Hi,
Does somebody see this error?
- Hartmut
gcc -c hal\halx86\mp\processor_mp.c -o
.\up\obj-i386\hal\halx86\mp\processor_mp.o -Ihal\halx86\include
-Intoskrnl\include -D_DISABLE_TIDENTSSMP -D_NTHAL_ -D__USE_W32API -I.
-Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers
-Iinclude\subsys -Iinclude\ndk -Iw32api\includ\include\crt
-Iw32api\include\ddk -D_M_IX86 -D_X86_ -D__i386__ -D_REACTOS_ -DDBG
-DKDBG -Wall -Wno-strict-aliasing -ftracer
-momit-leaf-fram-mpreferred-stack-boundary=2 -Wpointer-arith -g -pipe
-Werror -D_SEH_NO_NATIVE_NLG
hal\halx86\mp\mpconfig.c: In function `HaliScanForMPConfigTable':
hal\halx86\mp\mpconfig.c:563: internal compiler error: in
cfg_layout_merge_blocks, at cfgrtl.c:2631
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
_make: *** [.\up\obj-i386\hal\halx86\mp\mpconfig.o] Error 1
_make: *** Waiting for unfinished jobs....
gcc (GCC) 3.4.2 (mingw-special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Hi all,
I think this is important to share to the discussion. From one of the developers
with FreeDOS, Eric Auer.
Thanks,
James
-------- Original Message --------
Subject: [Freedos-user] re: FAT and other file systems
Date: Fri, 13 Jan 2006 17:16:34 +0100 (MET)
From: Eric Auer <eric(a)coli.uni-sb.de>
Reply-To: freedos-user(a)lists.sourceforge.net
To: freedos-user(a)lists.sourceforge.net
Hi James,
> > And I think it is not more difficult to write HFS or FFS in the kernel
> > of FreeDOS than ReiserFS or XFS or all the other candidates.
I would like to comment this as follows: The Linux kernel modules for
ext3+jbd take 131+59k of memory. Reiserfs takes 243k (243*1000 bytes,
too lazy to convert to units of 1024 bytes). On the other hand, FAT
core takes 38k and you use it with either MSDOS (8k) or VFAT (13k)
implementations. Only the VFAT (long file name enabled) module of
Linux is affected by the 3 MS patents mentioned on the MS homepage.
> There is no way around this, unless someone will write a disclaimer, "Before
> you install FreeDos, do you want to enable Fat32 Patented Features"?
Microsoft WANTS you to believe that they patented FAT32.
Actually they patented their clever but twisted way to store
short and long filenames in the same directory, in a way which
allows LFN-unaware operating systems to use the drive without
getting confused by the LFN data and usually also without
damaging the LFN data either. But you already point that out yourself:
> We are
> facing the same issue with Ros. When I use FreeDos, I use the basic 8.3
> file system, so I don't see that as a major problem. The point here is the
> patent is about LFN, basic 8.3 is not effected.
So the disclaimer would only be displayed when you install the DOSLFN
package: "Install DOSLFN, which might have patent issues?". FreeDOS as
a DOS operating system itself is not affected by that problem. Plus
MS does have a disclaimer about their licensing, too:
http://www.microsoft.com/whdc/hwdev/download/hardware/fatgen103.pdf
which is more than 5 years old by now...
allows you to be compatible to all their FAT (including LFN) stuff
for the purpose of booting, OS installation, diagnosis, firmware,
similar things. They also tell that making/installing operating
systems may use all aspects of FAT. You could see this in a pessimist
way (you are allowed to develop and compile your OS on a LFN enabled
host system) or in a more optimistic way (your operating system
itself is allowed to use LFN because it simply is an operating system).
MS is targetting two groups at the moment: Vendors of USB sticks who
preinstall files on their sticks, and vendors of cams and mp3 players
and similar devices. FreeDOS is neither of those. But I did notice
that my hardware mp3 player does not support LFN. It only shows the
id3 text, if available, as "long song name", and is limited to
showing the SHORT file name as song name otherwise. Looks like
the vendor of the player did not want to pay MS for each device.
Digicams have similar issues - they usually generate filenames
like dsc0815 dot jpg and store all extra "title/name" information
inside the file (jpeg comment, EXIF data...?).
Eric
PS: I assume that you mean ReactOS, the free open WinNT clone,
when you mention Ros. ReactOS without LFN would not be the same...
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Freedos-user mailing list
Freedos-user(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user