Parrel Port Printer

Tutorials Win: Microsoft Windows Forum

- Previous
 - 1
 - WinCE Kernel init problem Hi, I'm developing a Win CE platform for my Strong ARM target. In Platform Builder Debug Windows I obtain : Kernel debugger is waiting to connect with target. 0 PID:0 TID:0 ProcessorType=0b11 Revision=9 0 PID:0 TID:0 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8c141018 0 PID:0 TID:0 +OEMInit 0 PID:0 TID:0 Windows CE Firmware Init 0 PID:0 TID:0 Stack=0xFFFFC79C 0 PID:0 TID:0 Initialize timer used for delays in the HAL 0 PID:0 TID:0 InitClock... 0 PID:0 TID:0 Initialize driver globals area... 0 PID:0 TID:0 Firmware Init Done. 0 PID:0 TID:0 -OEMInit 0 PID:0 TID:0 Sp=ffffc7cc On serial port I obtain: ... Stack=8C067FA8h Jumping to Physical Address 0xC0141000h (Virtual Address 0x8C141000h)... +OEMKitlInit Stack=FFFFC768h CS8900: MAC Address: 22:0:33:0:44:0 iobase:0xa7000300 membase:0xa6000000 INFO: Probe: CS8900 is detected. INFO: CS8900_IO_MODE INFO: Init: CS8900_Init OK. ::: OEMEthInit() IP Address : 10.21.4.228 ::: OEMEthInit() Netmask : 255.255.255.0 Device HANDBOX17408, IP 10.21.4.228, Port 981 Calling EdbgInitDHCP -OEMKitlInit Host connected Host IP: 10.21.4.89, port 1307 KITLGlobalState == 0x61 KITL Initialized Windows CE Kernel for ARM Built on Mar 13 2003 at 22:54:19 OEMInit seems OK. I have same doubt about the value of stack pointer Sp=ffffc7cc. Is it correct ? After OEMInit, what function is called by kernel ? Is the problem only an insufficient stack size ? (before calling Kernel start I make ... ldr r0, =DRAM_BANK1A_C_VIRTUAL add sp, r0, #0x61000 mov r0, pc add r0, pc, #OEMAddressTable-(.+8); bl KernelStart ) Thanks Best Regards Dario Tag: Parrel Port Printer Tag: 42014
 - 2
 - build.dat corrupt database Hi, compiling my strong ARM platform I obtain the following error: BUILD: d:\wince420\platform\handbox_01\build.dat(5001): corrupt database (File error) What means ? Can I simply ignore it ? I try to delete build.dat file and giving a rebuild all this file is regenerated whithout problems. If I make another rebuild all the error reappears ! Thanks Best regards Dario Tag: Parrel Port Printer Tag: 42013
 - 3
 - Parallel port- byte mode printer read Hi, We have a APS Printer CP290MRS , We were able to read the status byte of the printer from the dataport by implementing byte mode in our test application inWindows 2000 successfully. When we try to read the status byte of the printer from the dataport by implementing byte mode in our test application in WIN CE 4.2, We were NOT getting the status on data port. The APS Printer CP290MRS uses compatibility mode to write to the printer and byte mode to read from the printer. We were able to write to the printer successfuly using WriteFile () API. But we were not able to read using ReadFile() API . After checking the parallel port device driver in WIN CE 4.2 for ReadFile, It was found the Driver funtions LPT_Read has a single statement which returns 0 ( Zero). Any help in this regard ( to read data from parallel port printer in byte mode ) is highly appreciated. With Warm Regards, Swamy T.K. Tag: Parrel Port Printer Tag: 42012
 - 4
 - HIVE GEODE 4.2 vs 4.1 IDE Harddrive mckendric The system hive worked on a Geode build using PB4.1 but locks up using PB 4.2 The target uses an IDE HardDrive for hive storage. In both PlatformBuilder 4.1 and 4.2, the hive registry settings are: ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="Documents and Settings\\system.hv" "PROFILEDIR"="Documents and Settings" "Start DevMgr"=dword:1 [$(PCI_BUS_ROOT)\Template\GeodeIDE] "Flags"=dword:1000 [$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0] "Flags"=dword:1000 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile] "MountFlags"=dword:2 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSREGHIVE In 4.2 the GEODE system locks up after Initializing the volume heap which is the last debug message output. 4294768981 ...FS: Registering file system Hard Disk, index 4, flags 0x00000002 4294768983 ...FILESYS: Device started. Boot file system ready. 4294768991 ...FSVOL: Opening existing volume 4294768993 ...FSVOL: Volume heap already initialized 4294768993 ...FSREG: Mounted ROM portion of system hive 4294768994 ...FILESYS: Loading system hive from Hard Disk\Documents and Settings\system.hv. 4294769027 ...ERROR: d:\mckendric\private\winceos\coreos\filesys\heap\.\volume.c line 461: 4294769027 ...FSVOL: Aborting init on non-volume 4294769028 ...FSREG: Mounting clean system hive 4294769029 ...BuildPath: Hard Disk 4294769029 ...FATFS!FAT_CreateDirectoryW(1 chars: \) returned FALSE (183) 4294769030 ...BuildPath: Hard Disk\Documents and Settings 4294769031 ...FATFS!FAT_CreateDirectoryW(23 chars: \Documents and Settings) returned FALSE (183) 4294769034 ...FSVOL: Opening existing volume 4294769034 ...FSVOL: Creating new volume 4294769177 ...FSVOL: Initializing volume heap 4294769207 ...FSREG: Taking down boot registry. Any open keys will be invalid. 4294769275 ...FILESYS: Registry in place. 4294769279 ...FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294769349 ...FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294769350 ...FSREG: Logging in default user. 4294769350 ...FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294769351 ...SetCurrentUser: Logging out (nobody), logging in default 4294769353 ...FSREG: Mounting ROM portion of user hive 4294769361 ...FSVOL: Opening existing volume 4294769363 ...FSVOL: Volume heap already initialized 4294769364 ...Mounting user hive from Hard Disk\Documents and Settings\default\user.hv 4294769373 ...ERROR: d:\mckendric\private\winceos\coreos\filesys\heap\.\volume.c line 461: 4294769374 ...FSVOL: Aborting init on non-volume 4294769375 ...FSREG: Mounting clean user hive 4294769377 ...FSVOL: Opening existing volume 4294769378 ...FSVOL: Creating new volume 4294769433 ...FSVOL: Initializing volume heap In 4.1 the boot up continues after this: 4294769711 ...FS: Registering file system Hard Disk, index 4, flags 0x00000002 4294769714 ...FILESYS: Device started. Boot file system ready. 4294769716 ...FSVOL: Opening existing volume 4294769718 ...FSVOL: Volume heap already initialized 4294769719 ...FSREG: Mounted ROM portion of system hive 4294769719 ...FILESYS: Loading system hive from Hard Disk\Documents and Settings\system.hv. 4294769758 ...FSVOL: Opening existing volume 4294769766 ...FSVOL: Volume heap already initialized 4294769772 ...FSREG: Mounted existing system hive 4294769772 ...FSREG: Taking down boot registry. Any open keys will be invalid. 4294769797 ...FILESYS: Registry in place. 4294769797 ...FSREG: Set persist value (0) 4294770028 ...FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294770028 ...FSREG: Logging in default user. 4294770029 ...FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294770030 ...SetCurrentUser: Logging out (nobody), logging in default 4294770045 ...FSREG: Mounting ROM portion of user hive 4294770047 ...FSVOL: Opening existing volume 4294770049 ...FSVOL: Volume heap already initialized 4294770050 ...Mounting user hive from Hard Disk\Documents and Settings\default\user.hv 4294770095 ...FSVOL: Opening existing volume 4294770100 ...FSVOL: Volume heap already initialized 4294770105 ...FSREG: Set persist value (0) 4294770188 ... Initializing Database 4294770192 ...Filesystem initialized! The relevant difference seems to be: ERROR: d:\mckendric\private\winceos\coreos\filesys\heap\.\volume.c Who is mckendric? Tag: Parrel Port Printer Tag: 42007
 - 5
 - Help! hi,all: I can't fine "struct LPVOID" that more files use it define a new structure in WinCE BSP c sources files,anybody who can tell me which file define the struct LPVOID.ths. Best Regards. lilo. Tag: Parrel Port Printer Tag: 41998
 - 6
 - Binary built in eVC 3.0-How to add the file for CEPC Platform? Dear Tech Gurus, I have a Driver(.dll) file build in eVC++ 3.0 in the x86 platform. Can I include that file in the CEPC? If so what changes I need to do in .bib file? Pls advice/suggest Thanks a tonne, Cheers, Lakshman Tag: Parrel Port Printer Tag: 41991
 - 7
 - How to know what peripherals are compatible with CE.Net 4.2...... Hi All, Where can i see what all peripherals that are can be compatible with my CE.NET 4.2 CEPC........ I understand that Microsoft has some details about peripherals on the microsoft.com , but would that be all the peripherals that can be added to a CEPC..... I am looking for peripherals like printers, ISDN Cards, WebCams etc... Kindly suggest, Raj.. Tag: Parrel Port Printer Tag: 41988
 - 8
 - about AER(advanced exception reporting) Dear Everyone: We are using the AER mechanism to capture the exception thrown by the application under the Windows for Automotive platform,and we know after AerSVC.exe exports the exception information to a text file(for example "a.txt"), and we can use the following command line to process this text file: perl aerreport.pl a.txt By this way,we can get the function name thrown the exception according its stack address.but now,a our customer ask us to translate the aerreport.pl file to .exe file in the win32 platform ,we don't know how to do it ,can everyone tell me how to do it or where are there some informations about it? thank you in advance. Tag: Parrel Port Printer Tag: 41987
 - 9
 - Driver for using IDE Harddrive via compact flash port Hello, I have a standard IDE harddrive connected to a Compact Flash port. I believe winCE should be able to support this but not sure how to get it working. HARDWARE: -PXA250 with SA1111 (based on Intel Lubbock dev board) -Connected A[2:0], D[15:0], IOWR, IORD, CE1, CE2, IOIS16, RESET, nIRQ to corresponding pins on SA1111. -Forced CD1 & CD2 low so winCE knows something is on Sock1 SOFTWARE: -winCE 4.2 using BSP provided with 4.2 for Intel Lubbock -Included in build : storage devices -> ATAPI PCI/IDE storage block driver, Compact Flash / PC Card Storage -included everything under "storage manager" in build RESULTS: -winCE comes up with dialog box to enter driver for device on socket 1. Not sure what to put here. The compact flash spec allows for devices operating in "true IDE" mode so this must be possible. Is there a proper driver for this in winCE 4.2? Tag: Parrel Port Printer Tag: 41986
 - 10
 - CEMON.EXE causing platform to crash! Hello, I've got an SH4 platform that I would like to be able to do application degugging on. Using either the manual or CESH server I am able to establish a connection and all of the appropriate files are downloaded automatically (my application ,cemon.exe and JITdebugger). As soon as I try to establsih a debugging connection and use it to debug my app, it appears as though cemon causes an exception in coredll. Has anyone come across this before or can anyone suggest a possible reason for this? As CEMON is provided in binary form, I have no way to debug this... Regards, Glenn. Tag: Parrel Port Printer Tag: 41985
 - 11
 - how to replace midi player in Win CE ? How to replace midi player in Win CE ? I want to use my own midi decoder to replace the default setting in Win CE, so I can improve the sound quality of midi playing. Is there any way to do this ? Any advice will be greatly appreciated ! Tag: Parrel Port Printer Tag: 41984
 - 12
 - Help with SNMP Registry Keys How do you get the SNMP service to recognize changes to the registry keys after adding new extension agents? Do you need to reboot or is there an IOCTL command. I noticed that SNMP is not running as a system service so I cannot use service control commands; I did not regonize any SNMP entries in the services registry key. I would like to do this programmatically because I am working in the emulator. Thanks Tag: Parrel Port Printer Tag: 41978
 - 13
 - PB 4.2 Emulator woes. This all worked so well w/PB 4.0. Then I upgraded to 4.2 :( I built a shiny, new emulator image based on Internet Appliance config. My emulator is configured w/resolution of 800X600, has 48 MB of memory, has wired LAN, and is KITL and Kernel Debugger-enabled. When I try to download/initialize, I get the debug spew at the end of this message, and then wait. After about 5 minutes or so, the emulator pops up a message box that reads: "An unrecoverable processor error has been encountered. The PC will now reset." Any help? TIA, M Kernel debugger is waiting to connect with target. 0 PID:0 TID:0 CEPC Firmware Init 0 PID:0 TID:0 RTC - Status Reg B - 0x02 0 PID:0 TID:0 PCIBIOS:: BIOS Address static map to addr=a00e0000 0 PID:0 TID:0 GetPicRoutingIrqTable: Start 0 PID:0 TID:0 search_pci_bios start 0 PID:0 TID:0 search_pci_bios end fails 0 PID:0 TID:0 GetPicRoutingIrqTable: FAILS!!! 0 PID:0 TID:0 Firmware Init Done. 0 PID:0 TID:0 Looking for rom chain 0 PID:0 TID:0 Rom chain NOT found 0 PID:0 TID:0 Booting Windows CE version 4.20 for (x86) 0 PID:0 TID:0 &pTOC = 80245a78, pTOC = 81a4173c, pTOC->ulRamFree = 81a81000, MemForPT = 00004000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 Configuring: Primary pages: 9591, Secondary pages: 0, Filesystem pages = 4795 0 PID:0 TID:0 Booting kernel with clean memory configuration: 0 PID:0 TID:0 Memory Sections: 0 PID:0 TID:0 [0] : start: 81a86000, extension: 00003000, length: 02577000 0 PID:0 TID:0 X86Init done, OEMAddressTable = 802ab7b8. 0 PID:0 TID:0 Windows CE KernelInit Tag: Parrel Port Printer Tag: 41974
 - 14
 - QFE 030915_KB828098 Doesn't Fully Address 64-bit Integer Multiplication Problems Over the last year, there has been some discussion in the newsgroups about a time conversion bug in COREDLL for debug builds. Just in the last week, we diagnosed the two bugs -- one in the Windows CE code and one in the ARMV4I compiler -- that were causing this (and other related problems). Coincidentally, Microsoft just released QFE 030915_KB828098 for 4.2 that attempts to address the problem, but it does so unsatisfactorily, for several reasons: - it doesn't fix the problem in CE .NET 4.1, only in 4.2 - it doesn't fix the offending CoreMain code properly; it hacks around the problem - the same offending code exists in other places in Windows CE, which this QFE doesn't fix - it doesn't fix the underlying ARMV4I compiler bug, which still exists We'd like to see new QFEs released in the next few months that address this properly, for all affected parts of Windows CE as well as the compiler, and for 4.1 and 4.2 (this may also appear in 4.0, but we didn't check). What follows below is the definition of the two bugs that caused the behavior, but which still have not been fixed fully even with the new QFE applied. BUG 1: mul64_32_64 uses (__int64) instead of (unsigned __int64) The function mul64_32_64 in time.c, which is part of COREDLL in the private area, multiplies a 64-bit FILETIME value by a 32-bit DWORD, and does by multiplying the dwLowDateTime and dwHighDateTime fields of FILETIME with the DWORD separately, then adding them together appropriately. In order to do this, it must first cast the 32-bit values used in the multiplication to a 64-bit value, so that the compiler will not throw out the overflow above 32-bits, as it usually does with 32-bit multiplicaiton. The bug is that mul64_32_64 casts these values to (__int64), which is signed; it should be casting them to (unsigned __int64) and using an unsigned __int64 temporary variable for accumulating the results. As a result, the multiplicaiton is done using the smull instruction, which sign extends the result. Therefore, if bit 31 of the dwLowDateTime is set, the result of this first step will be a negative number. When this result is added to the result of the multiplication between the DWORD and dwHighDateTime, it will subtract rather than add to this value, which is incorrect. As an example, if the FILETIME arg contains the 64-bit number 0xb8e8b296740 and this is multiplied by 0x2710, the result should be 0x1c3701c01513400, but mul64_32_64 returns 0x1c3490c01513400 in this case. The reason is that, as a first step, mul64_32_64 takes the low 32-bits of FILETIME and 0x8b296740 and multiplies it with 0x2710. But before it does this, it casts both operands to __int64, which causes the processor to treat the first operand as a negative number. The result of this multiplication should be 0x0000153c01513400 to achieve the proper result, but will actually be 0xffffee2c01513400, yielding the incorrect result above. So, if that's the fix, what's the problem with Microsoft's QFE patch? Besides only addressing 4.2, there are two more fundamental issues: A) Microsoft's QFE does not fix this by changing the __int64 values to unsigned __int64, as the purpose of the function clearly requires. Instead, it hacks around this by changing separating the casting of the values to __int64 from the multiplication. Of course, that shouldn't make any difference, since they are still casting them as signed __int64 values, but it turns out it does (see the Bug #2 described below). B) Microsoft's QFE only patches this in the version of mul64_32_64 that from time.c in CoreMain. It doesn't fix it in the version of mul64_32_64 from dhcp.c in Windows CE's DHCP code. C) Microsoft also uses __int64 elsewhere in the OS, so it's possible that this same issue -- assuming that int64's are unsigned -- could occur elsewhere. It might make sense for Microsoft to explicitly define all 64-bit variables in CE as "unsigned" unless they know that these variables must support negative numbers. BUG2: The ARMV4I Compiler Handles 64-bit Integer Multiplication Incorrectly In Retail Builds Before we start with how Microsoft's QFE is able to work despite incorrect code, let's look at why the original code worked in retail builds, but not debug builds, despite the problem described above, since that illustrates a problem with the ARMV4I handling of 64-bit multiplication. In the bug above, the first part of mul64_32_64, as originally implemented, resolves to the simplified code below: __int64 result; DWORD op1, op2, op3; ... result = (__int64) op1 * (__int64) op2; result += ((__int64) op3 * (__int64) op2) << 32; In a debug build, the above multiplication operations are generated using ARM smull instructions, which perform a multiplication of two signed 32-bit integers and yield a signed 64-bit result. Since __int64 is a signed data type, these instructions match the source code. But when you compile the above code in a retail build, the above operations are generated as follows: umull r2, r0, r3, r1 mla r1, r4, r1, r0 In other words, umull is being used for the first operation, which is incorrect given that the operands and the result of the first operation are all signed integers. So mul64_32_64 should have been using unsigned __int64 values all along, but this second bug saved the day for retail builds on the ARMV4I version of CE by forcing an unsigned multiplication despite what the source code indicated. And, of course, it turns out that Microsoft's QFE is saved by the same compiler bug. In the patch, Microsoft replaces the above code with, essentially, this: __int64 result, m1, m2; DWORD op1, op2, op3; ... m1 = op1; m2 = op2; result = m1 * m2; result += ((__int64) op3 * (__int64) op2) << 32; The reason this works for both debug and retail builds is that, in this case, the unsigned values of op1 and op2 are assigned to signed 64-bit variables, something the ARMV4I compiler knows how to do correctly. In this case, even if bit 31 of either op1 or op2 is set to 1, the compiler does not treat these values as negative. So m1 and m2 both end up with positive integers, and m1 * m2 works fine for both debug and retail builds. But the ARMV4I compiler error for 64-bit multiplication still rears its head even with Microsoft's QFE in place. If you look at the instructions generated for a debug build of the above code, it's clearly performing the multiplicaiton of m1 and m2 as signed integers (it requires about 16 instructions, including three multiplication instructions). In the case of a retail build of the same code, however, the multiplication operation generates: umull r2, r0, r1, r4 mla r1, r3, r4, r0 In other words, Microsoft's QFE is a workaround (and not the best one) for the fact that the ARMV4I compiler treats __int64 as a signed integer in debug builds, and as an unsigned integer in retail builds, when performing integer mutliplication. Whether the ARMV4I compiler handles this correctly for other operations on __int64 integers is something we haven't explored. Clearly, this is a serious issue considering the extent to which Microsoft uses __int64 values in Windows CE code, since it causes the operating system to function differently when debugging than for retail builds. It also creates an issue for developers working with 64-bit integers in our own code: we originally tried to use them in an iButton driver earlier this year, but wound up storing the iButton's 64-bit ID as two separate 32-bit integers because of flakiness with 64-bit arithmetic. Nathan Tennies Director, Software Engineering InHand Electronics (240) 558-2014 x.215 (240) 558-2019 (fax) Tag: Parrel Port Printer Tag: 41968
 - 15
 - Xscale, PSM & Hive Registry I've run into a strange condition on two different reference platforms, both based on the PXA255 cpu, but using different code bases under CE .Net 4.1 (one is the Wince 4.1 XSC1BD, the other is a 3rd party package). Both platforms worked fine with RAM based registries. Then I switched over to Hive based registries, with the hives stored in the PSM file system. To enable and disable the PSM as the destination for the Hives, I either set to 1 or 0, respectively, the "Start DevMgr" value under [HKEY_LOCAL_MACHINE\Init\BootVars]. If I enable the Hive on PSM, the system generates several DEBUGCHKs while booting, and I lose the use of ActiveSync over USB on one device. The USB driver appears to be loaded and running, but I cannot connect to the desktop, and if I open the Networking control panel and try to manually create a new connection, the USB device is not shown as an option. On the second system, I lose use of the Compact Flash slot. If I disable the device manager ( so the Hive winds up in RAM), everything works just fine. In both systems, I delete the Hive stored in the PSM, re-enable the device manager (just to be sure I'm not looking at leftover/old registry data). I also downloaded and exported the registries, both with and without the device manager active. I did notice something different between the two: With the one with the device manager active (i.e. USB not functional), the two following keys exists that were not in the other version: [HKEY_LOCAL_MACHINE\Drivers\Active\15] "Hnd"=dword:003ad7f0 "Key"="Drivers\\BuiltIn" "ClientInfo"=dword:00000000 [HKEY_LOCAL_MACHINE\Drivers\Active\21] "Hnd"=dword:003ad860 "Key"="Drivers\\BuiltIn\\TAPI" "ClientInfo"=dword:00000000 The DEBUGCHK messages are: 4294785347 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for api set id 23. 4294785349 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed in file d:\jameson\private\winceos\comm\tapi\tapi\init.c at line 643 4294787589 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for api set id 19. 4294787590 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed in file d:\jameson\private\winceos\comm\pm\lib\peginit.c at line 402 4294789722 PID:23ad28e6 TID:c39a7fd6 0x83998400: Unknown: DEBUGCHK failed in file d:\jameson\private\winceos\comm\pm\lib\buffers.c at line 256 Any idea what this is about? Thanks Tag: Parrel Port Printer Tag: 41959
 - 16
 - partition count limitation under CE.NET Hi, I have done extensive research on the FAT16 file system. I have found no evidence that there exists a limit (other than physical disk capacity) for the number of partitions that FAT16 supports. That is, from a strict FAT16 design point of view, once the primary partition is created and defined, any number of extended partitions, up to the maximum partition size limitation of roughly 2 GB, can be created and accessed. Granted, this assessment relies on the fact that there are typically several places that C/H/S (cylinder/head/sector) get converted to LBA and vice-versa. This depends on the ATA drive, BIOS, and OS. Fom a CE.NET point of view, the implementation of the FSD/FSDM/PartManager could limit the number of partitions based on some arbitrary value. Although I did not find any such limitation while digging through the FSD/FSDM/PartManager code, I could have missed it. Does anyone know of a limitation to the number of partitions that the CE.NET file system subsystem imposes? If so, what is it? I have a few that I can think of (again no proof). 1. Since all file systems are mounted under the root, there could be a limitation due to the maximum number of folders allowed off of the root. This could be imposed by the storage manager or the FSDM. 2. Assuming that the Partition Manger enumerates all the links in the FAT chain, my guess is that for CE.NET, there could be an upper limit somewhere between 62 and 68 because of the so-called 137 MB limitation imposed by most modern ATA devices. 137 MB is a result of using 28 bits for sector addressing (note: ATA-6 defines 48 bits). So, depending on how big you make the partition (somewhere between 2 and 2.2 GB) you'll end up with a number between 62 and 68. 3. Hardware BIOS limitations. Certain BIOS implementations could not be providing extended int 13 disk services. Int 13 is x86 based. I don't know how other processors (specifically ARM) provide BIOS disk support. Any additional information on this would be helpful. Thanks, Nick. Tag: Parrel Port Printer Tag: 41958
 - 17
 - PB 4.2 Emulator woes. (Reposted - didn't seem to work the first time) This all worked so well w/PB 4.0. Then I upgraded to 4.2 :( I built a shiny, new emulator image based on Internet Appliance config. My emulator is configured w/resolution of 800X600, has 48 MB of memory, has wired LAN, and is KITL and Kernel Debugger-enabled. When I try to download/initialize, I get the debug spew at the end of this message, and then wait. After about 5 minutes or so, the emulator pops up a message box that reads: "An unrecoverable processor error has been encountered. The PC will now reset." Any help? TIA, M Kernel debugger is waiting to connect with target. 0 PID:0 TID:0 CEPC Firmware Init 0 PID:0 TID:0 RTC - Status Reg B - 0x02 0 PID:0 TID:0 PCIBIOS:: BIOS Address static map to addr=a00e0000 0 PID:0 TID:0 GetPicRoutingIrqTable: Start 0 PID:0 TID:0 search_pci_bios start 0 PID:0 TID:0 search_pci_bios end fails 0 PID:0 TID:0 GetPicRoutingIrqTable: FAILS!!! 0 PID:0 TID:0 Firmware Init Done. 0 PID:0 TID:0 Looking for rom chain 0 PID:0 TID:0 Rom chain NOT found 0 PID:0 TID:0 Booting Windows CE version 4.20 for (x86) 0 PID:0 TID:0 &pTOC = 80245a78, pTOC = 81a4173c, pTOC->ulRamFree = 81a81000, MemForPT = 00004000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 Configuring: Primary pages: 9591, Secondary pages: 0, Filesystem pages = 4795 0 PID:0 TID:0 Booting kernel with clean memory configuration: 0 PID:0 TID:0 Memory Sections: 0 PID:0 TID:0 [0] : start: 81a86000, extension: 00003000, length: 02577000 0 PID:0 TID:0 X86Init done, OEMAddressTable = 802ab7b8. 0 PID:0 TID:0 Windows CE KernelInit Tag: Parrel Port Printer Tag: 41956
 - 18
 - .reg file question I have created a driver DLL and added to my platform as a feature. I am editing project.bib and project.reg to get the driver loaded when my CEPC starts. I used the settings found in the parallel driver's reg file as a starting point. Some of the entries here are required by the device manager that loads the device drivers, others I suspect, are used by the driver itself. DeviceArrayIndex, Prefix, Dll, and Order are understood. My settings happen to be 0, MPG, TenMpeg.dll, and ffff. Since I don't have any hardware yet, IoBase, IoLen, and SysIntr are not included. Will having these entries not present in the registry cause a problem with the device manager or the resource manager? I don't know what 'DeviceType' is used for. Is this the value set when a driver is added to a BSP? For example, I added the variable BSP_TENMPEG with the value 1 while adding a new device in the BSP wizard. Is this value (1) used for the DeviceType entry in the project.reg file? FriendlyName needs to be set to something. It seems like I have to create the folder structure and the .str files for the localization files. Is this correct? DevConfig is an unknown. I assume it is used by the driver manager because the entries for the parallel and the serial .reg files are the same. Help for the serial driver shows that these are used by RAS. Is this required? Thanks, Nick. Tag: Parrel Port Printer Tag: 41953
 - 19
 - generic vga - ce 4.1 Hi, I require a generic vga driver for a wince 4.1 x86 platform. As an example, CE 3.0 had such a driver: vga8bpp but it is not sipped with 4.1. Can this driver be used in 4.1? Is there a current version of same? If so, what's the proper way of adding it to the image build? Thanks /Boyd Tag: Parrel Port Printer Tag: 41944
 - 20
 - ISDN Connectivity to a CEPC.....How..?? Hi, How can we add ISDN Modem to a CEPC,..?? Are there any drivers specifically for the ISDN Modems like the PCL printer drivers.... anybody who has worked on this please reply.... --Raj. Tag: Parrel Port Printer Tag: 41941
 - 21
 - raw ir allocated by IrCOMM... how to release it ? Hi, When WinCE 4.2 boots with IrDA support, the IrCOMM component opens the raw IR port. A 3rd party application requires raw IR access too. Is it possible for us to force IrCOMM to release the raw IR port allocation (disable it). Then the 3rd party application would be able to open our raw IR port. After the 3rd party application is done, we would like to tell IrCOMM to open the raw IR port again (enable it). Is such a scheme possible ? I am asking because I think I approach this too difficult. The difficult way would be to create two virtual COM ports that interface to the same IrDA transceiver hardware. One would be for IrCOMM then, and one for the 3rd party application. When the 3rd party application would open the virtual COM port, then the virtual COM port for IrCOMM would 'disconnect' itself from the IrDA transceiver hardware and let the 3rd party COM port get control over it. IrCOMM would then not notice anything (except that it doesn't get any IrDA input and all IrDA output just disappears...). Please enlighten me. Can someone make me happy by telling me there is an easy way ? I think I'm just not seeing it right now. Thank you ! Ronald Tag: Parrel Port Printer Tag: 41940
 - 22
 - booting of nk.bin from CEPC BOARD and exporting an SDK. Hello all, Part 1) : I am facing problem in booting from harddisk.for the CEPC Board. i.e i am trying for , load CEPC NK.bin. even, i make BOOT PARTITION AS C , and the partition as active , and i place a BOOT LOADER, i.e bldr . after i make a setupdisk from wince. i run, mkdisk , which internally calls cesys.exe which assigns boot loader at -b: 62 offset - bootsect.img bldr c: and even i transfer the nk.bin file.., to the harddisk and if i try to boot the disk , i get an error message , Unable to load the boot loader.. could u please , help me out... Part 2): And secondly, once i make a customized platform, and for the platform generated, if i try to configure a SDK for the generated platform.i am able to do that and even i can build the configured SDK, and now since , the SDK is build properly, i view my newly generated SDK , in EVC++ 4.0,but if i try to run an application for the newly generated SDK, my application does not run properly..i.e my application is compiled properly but unfortunately ,if i try to download on to the device and configure with CESH SERVER, and configuring the transport part as KITL OR AS TCP/IP , i observe that , i am not able to establish the connectivity for the download.. hope , that u may guide me out.. thanks in advance.. eagerly waiting , for the reply .. -- Kallesh N. Patil Sr Software Engineer Email : kallesh@oranetech.com Orane Technologies Pvt Ltd. #25, 1st floor,7th cross,2nd main, 1 Stage ,Indiranagar Bangalore 560038 India Ph: +91 80 5252886/ 5271966. Fax: +91 80 5252894. Url: www.orantech.com Tag: Parrel Port Printer Tag: 41938
 - 23
 - about pcmcia Dear all: I have a PCMCIA card reader. It is the PCI interface and can access i82365. But the i82365 is the ISA interface,how can I change it to PCI. Tag: Parrel Port Printer Tag: 41937
 - 24
 - Thread safety in device driver functions (XXX_Open, XXX_Close) Does device.exe serialize access to my device driver's exported functions? I need to modify a global data structure in XXX_Open and XXX_Close, should I add my own synchronization around that, or will device.exe do that for me? Thanks in advance. Tag: Parrel Port Printer Tag: 41936
 - 25
 - 320 x 200 Hi All, Here a problem with the resolution of the targetPC. After loading the CEPC image on PIII system it only works in 320 x 200 mode. No mather what is been changed in the LOADPC (resolution), it always turns to 320 x 200. What can I do? Thanks a lot and best regards, Tag: Parrel Port Printer Tag: 41934
- Next
 - 1
 - SRAM Card Hi I am attemting to use an of the shelf SRAM Pcmcia Card (Mitsubishi 512KB, MF3513-LYCAT01) in our hardware Wince 3.0, StrongARM based. When I plug it in to the pcmcia slot all I get is a dialog, Unidentified PCCard Adapter Enter the name of the driver for this PCCard and an option to enter the driver name. I would appreciate any help on this, what do I need to set up in platform.reg?, which driver do I use? Has anyone use these before. Regards Tariq Tag: Parrel Port Printer Tag: 41933
 - 2
 - TransmitFile Is this supported in CE 4.2? If so, what are the libraries and include files. Thanks Tag: Parrel Port Printer Tag: 41932
 - 3
 - Emulator Incoming and Outgoing Network Config I am have a problem with configuring the emulator to support both incoming and outgoing network. My configuration is: I have CE 4.2 with eVC++ SP2 installed on a XP machine. The XP machine has 2 network cards with Virtual PC Emulated Ethernet Switch on both and a third cable network connection with no Virtual PC Emulated Ethernet Switch. Only one network card is connected to a network. My emulator is configured with Fixed IP address and Virtual Switch. However, I am unable to connect to my emulator. If I change to NAT Outgoing only, it works but I am unable to have incoming network (as expected). The same emulator configuration works on other computers that have Win2K and one network card. Thanks Tag: Parrel Port Printer Tag: 41931
 - 4
 - regarding booting of NK.bin on CEPC hardware and Exporting SDK, for custosmised platform. Hello all, Part 1) : I am facing problem in booting from harddisk.for the CEPC Board. i.e i am trying for , load CEPC NK.bin. even, i make BOOT PARTITION AS C , and the partition as active , and i place a BOOT LOADER, i.e bldr . after i make a setupdisk from wince. i run, mkdisk , which internally calls cesys.exe which assigns boot loader at -b: 62 offset - bootsect.img bldr c: and even i transfer the nk.bin file.., to the harddisk and if i try to boot the disk , i get an error message , Unable to load the boot loader.. could u please , help me out... Part 2): And secondly, once i make a customized platform, and for the platform generated, if i try to configure a SDK for the generated platform.i am able to do that and even i can build the configured SDK, and now since , the SDK is build properly, i view my newly generated SDK , in EVC++ 4.0,but if i try to run an application for the newly generated SDK, my application does not run properly..i.e my application is compiled properly but unfortunately ,if i try to download on to the device and configure with CESH SERVER, and configuring the transport part as KITL OR AS TCP/IP , i observe that , i am not able to establish the connectivity for the download.. hope , that u may guide me out.. thanks in advance.. eagerly waiting , for the reply .. -- Kallesh N. Patil Sr Software Engineer Email : kallesh@oranetech.com Orane Technologies Pvt Ltd. #25, 1st floor,7th cross,2nd main, 1 Stage ,Indiranagar Bangalore 560038 India Ph: +91 80 5252886/ 5271966. Fax: +91 80 5252894. Url: www.orantech.com Tag: Parrel Port Printer Tag: 41927
 - 5
 - Activesync connection problem on Assabet using USB I use PB4.1 to build a CE image for the Assabet. I have installed Activesync 3.5 to set up Activesync connection via USB. Problem: When I plug in the USB cable, the host PC recognizes it as an unknown USB device. How can this connection problem be solved? Here are questions in detail. 1. How can I determine vendor ID and product ID to define the three sections in 'wceusbsh.inf' of host PC? 2. What kind of addition(or modification) is necessary for the registry of Assabet? 3. If any, is it possible to get sample files for 'wceusbsh.inf' and the modified WinCE registry? Thank you for any information in advance. Tag: Parrel Port Printer Tag: 41926
 - 6
 - Using a Compact Flash on Lubbock with WinCE Hello, I have a design based on lubbock (PXA250, SA-1111, etc) with winCE 4.2. -using the BSP that comes with 4.2. -I can talk to the PCMCIA slot perfectly - read CIS, etc -If I install a "compact flash" card into the CF slot and read the "status reg" using card & socket services, it says that only socket0 has a card. -I did the obvious like get a 2nd CF card and check the voltage. Before I break out the logic analyzer, I want to make sure I am not doing anything obviously wrong. Does CF require a special "enabling" or is there a known issue with the CF slot? Thanks in advance, -Jeff Tag: Parrel Port Printer Tag: 41924
 - 7
 - Buy Platform Builder 4.1 Hello! We have BSP installer for our WCE borad only for Platform Builder 4.1. The BSP installer make error during installation (my coputer have Platform Builder 4.2 NET) Now on Microsoft site i found only Platform Builder 4.2 NET. Where may buy Platform Builder 4.1. Thank you. Tag: Parrel Port Printer Tag: 41922
 - 8
 - newbe to xp embedded I am part of a senior project group who is just starting to become familiar with xp embedded software. I was wondering where a good resource for answers is, so I don't have to post all of my questions in this group. any suggestions would be great!! thanks!! Tag: Parrel Port Printer Tag: 41920
 - 9
 - about sources file Hi, dear all, in the win ce .net help doc says : ============================================ Conditional statements in sources files are not supported. The following code example shows that Build.exe ignores the first, second, fourth, and sixth lines, and appends the SOURCES macro twice. # Bad example !IF "$(LOCALE)" == "0409" SOURCES= $(SOURCES) us-src.c !ELSE SOURCES= $(SOURCES) inter-src.c !ENDIF ==================================== However, !IF and !ELSE is used in every sample source files. for example : =================================== DOSYSGEN=1 !IFDEF DOSYSGEN TARGETNAME = KBDHID_LIB TARGETTYPE = LIBRARY TARGETDEFNAME = KBDHID DEFFILE=$(TARGETDEFNAME).def WINCETARGETFILE0=$(_COMMONOAKROOT)\lib\$(_CPUINDPATH) \$(TARGETDEFNAME).def !ELSE TARGETNAME = KBDHID TARGETTYPE = DYNLINK TARGETLIBS = \ $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib \ DLLENTRY = DllEntry !ENDIF SOURCES= \ kbdhid.cpp \ kbd.cpp \ ======================================= What is this going on? Is this the reason that I only get KBDHID_LIB.lib, but doesn't get KBDHID.dll? But it seems not. Help, I just can't get my kbdhid.dll KY Tag: Parrel Port Printer Tag: 41918
 - 10
 - Application debugging using KITL Hi eveyone, Is it possible to use kitl to debug an application using EVC4 only (ie no platform builder present on the system)? From what I can see, you seed PB to start up the 3 kitl services (CESH, DBG & DBGMSG) before it becomes of any use to EVC4.0... Is this correct or is there some way of using KITL to acheive application debugging? Thanks, Glenn. Tag: Parrel Port Printer Tag: 41908
 - 11
 - Take a look at correction update --qpuakeaagt Content-Type: multipart/related; boundary="dwgjtarlvecb"; type="multipart/alternative" --dwgjtarlvecb Content-Type: multipart/alternative; boundary="ljlrutzlw" --ljlrutzlw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Microsoft Customer this is the latest version of security update, the "September 2003, Cumulative Patch" update which fixes all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three new vulnerabilities. Install now to continue keeping your computer secure from these vulnerabilities. This update includes the functionality = of all previously released patches. System requirements: Windows 95/98/Me/2000/NT/XP This update applies to: - MS Internet Explorer, version 4.01 and later - MS Outlook, version 8.00 and later - MS Outlook Express, version 4.01 and later Recommendation: Customers should install the patch = at the earliest opportunity. How to install: Run attached file. Choose Yes on displayed dialog box. How to use: You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles = can be found on the Microsoft Technical Support web site. http://support.microsoft.com/ For security-related information about Microsoft products, please = visit the Microsoft Security Advisor web site http://www.microsoft.com/security/ Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable = to respond to any replies. ---------------------------------------------- The names of the actual companies and products mentioned = herein are the trademarks of their respective owners. Copyright 2003 Microsoft Corporation. --ljlrutzlw Content-Type: text/html Content-Transfer-Encoding: quoted-printable <HTML> <HEAD> <style type=3D'text/css'>.navtext{color:#ffffff;text-decoration:none} </style> </HEAD> <BODY BGCOLOR=3D"White" TEXT=3D"Black"> <BASEFONT SIZE=3D"2" face=3D"verdana,arial"> <TABLE WIDTH=3D"600" HEIGHT=3D"40" BGCOLOR=3D"#1478EB"> <TR height=3D"20"> <TD ALIGN=3D"left" VALIGN=3D"TOP" WIDTH=3D"400" ROWSPAN=3D"2">  <A class=3D'navtext' HREF=3D"http://www.microsoft.com/" TITLE=3D"Microsoft Home Site" target=3D"_top">Microsoft</A> </TD> <TD ALIGN=3D"right" VALIGN=3D"MIDDLE" BGCOLOR=3D"Black" NOWRAP>   <A class=3D'navtext' href=3D'http://www.microsoft.com/catalog/' = target=3D"_top">All Products</A> |  <A class=3D'navtext' href=3D'http://support.microsoft.com/' = target=3D"_top">Support</A> |  <A class=3D'navtext' href=3D'http://search.microsoft.com/' = target=3D"_top">Search</A> |  <A class=3D'navtext' href=3D'http://www.microsoft.com/' target=3D_top> Microsoft.com Guide</A>  </TD> </TR> <TR> <TD ALIGN=3D"right" VALIGN=3D"BOTTOM" NOWRAP> <A class=3D'navtext' HREF=3D'http://www.microsoft.com/' TARGET=3D" top"> Microsoft Home</A>   </TD> </TR> </TABLE>  <IMG SRC=3D"cid:kpkcfnh" BORDER=3D"0"> <TABLE WIDTH=3D"600"><TR><TD> Microsoft Customer this is the latest version of security update, the "September 2003, Cumulative Patch" update which fixes all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three new vulnerabilities. Install now to continue keeping your computer secure from these vulnerabilities. This update includes the functionality = of all previously released patches. </TD></TR> </TABLE> <TABLE BORDER=3D"1" CELLSPACING=3D"1" CELLPADDING=3D"3" WIDTH=3D"600"> <TR VALIGN=3D"TOP"> <TD NOWRAP><IMG SRC=3D"cid:tbhawse" = ALIGN=3D"absmiddle" BORDER=3D"0"> System requirements </TD> <TD NOWRAP>Windows 95/98/Me/2000/NT/XP</TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><IMG SRC=3D"cid:tbhawse" = ALIGN=3D"absmiddle" BORDER=3D"0"> This update applies to </TD><TD NOWRAP> MS Internet Explorer, version 4.01 and later MS Outlook, version 8.00 and later MS Outlook Express, version 4.01 and later </TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><IMG SRC=3D"cid:tbhawse" = ALIGN=3D"absmiddle" BORDER=3D"0"> Recommendation</TD> <TD NOWRAP>Customers should install the patch = at the earliest opportunity.</TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><IMG SRC=3D"cid:tbhawse" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to install</TD> <TD NOWRAP>Run attached file. = Choose Yes on displayed dialog box.</TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><IMG SRC=3D"cid:tbhawse" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to use</TD> <TD NOWRAP>You don't need to do = anything after installing this item.</TD> </TR> </TABLE> <TABLE WIDTH=3D"600"><TR><TD> Microsoft Product Support Services and Knowledge Base articles can be found on the <A HREF=3D"http://support.microsoft.com/" = TARGET=3D"_top">Microsoft Technical Support</A> web site. = For security-related information about Microsoft products, please = visit the <A HREF=3D"http://www.microsoft.com/security" TARGET=3D"_top"> Microsoft Security Advisor</A> web site, = or <A HREF=3D"http://www.microsoft.com/contactus/contactus.asp" = TARGET=3D"_top">Contact Us.</A> Thank you for using Microsoft products. Please do not reply to this message. = It was sent from an unmonitored e-mail address and we are unable = to respond to any replies. <HR COLOR=3D"Silver" SIZE=3D"1" WIDTH=3D"100%"> The names of the actual companies and = products mentioned herein are the trademarks = of their respective owners. </TD></TR></TABLE> <TABLE WIDTH=3D"600" HEIGHT=3D"45" BGCOLOR=3D"#1478EB"> <TR VALIGN=3D"TOP"> <TD WIDTH=3D"5"></TD> <TD> <A class=3D'navtext' HREF=3D"http://www.microsoft.com/= contactus/contactus.asp" TARGET=3D"_top">Contact Us</A>  |  <A class=3D'navtext' HREF=3D"http://www.microsoft.com/legal/" = TARGET=3D"_top">Legal</A>  |  <A class=3D'navtext' HREF=3D"https://www.truste.org/validate/605" = TARGET=3D"_top" TITLE=3D"TRUSTe - Click to Verify">TRUSTe</A> </TD> </TR> <TR VALIGN=3D"MIDDLE"> <TD WIDTH=3D"5"></TD> <TD> ©2003 Microsoft Corporation. All rights reserved. <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= info/cpyright.htm" TARGET=3D"_top">Terms of Use</A>  |  <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= info/privacy.htm" TARGET=3D"_top"> Privacy Statement</A> |  <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= enable/" TARGET=3D"_top">Accessibility</A> </TD> </TR> </TABLE> </BODY> </HTML> --ljlrutzlw-- --dwgjtarlvecb Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <kpkcfnh> R0lGODlhaAA7APcAAP///+rp6puSp6GZrDUjUUc6Zn53mFJMdbGvvVtXh2xre8bF1x8cU4yLprOy zIGArlZWu25ux319xWpqnnNzppaWy46OvKKizZqavLa2176+283N5sfH34uLmpKSoNvb7c7O3L29 yqOjrtTU4crK1Nvb5erq9O/v+O7u99PT2sbGzePj6vLy99jY3Pv7/vb2+fn5++/v8Kqr0oWHuNbX 55SVoszN28vM2pGUr7S1vqqtv52frOPl8CQvaquz2Ojp7pmn3Ozu83OPzmmT6F1/xo6Voh9p2C5z 3EWC31mS40Zxr4uw6LXN8iZkuXmn55q97PH2/Yir1rbL5iVTh3Oj2cvX5Pv9/+/w8QF8606h62Wk 3n+dubnY9abB2c7n/83h9Nji6weK+CGJ4Vim6WyKpKWssgFyyAaV/0Km8Gyx6HW57FJxicDP2+Tt 9Pj8/wOa/wmL5wqd/w6V8heb91e5+mS9+VmLr4vD6qvc/b/j/Mbn/sTi9rvX6szq/tPt/9ju/dzx /+n2/+74//P6/+3w8hOh/xOW6yCm/iuu/zWv/0m4/XTH/IXK95TP9qPV9bfi/tDn9tfp9OP0/93r 9L3Izy6Vzj22/lrC/mfG/JvJ5JGntAyd6IbX/3zD6GzP/3jV/2uoxHqbqujv8g6MvJTj/2HF5pXV 606zz6Hp/63v/7j1/8Ps88b8/rbj5RKOkE2wr3OGhoKGhv7///Dx8V2alqvm4Zni1YPRvx5uVwyO X0q2hLTvw8X10gx2H4PXkkuoV5zkoQeADZu7mmzIVEO7HIXbaGfLMPz8+97d2/Px7v///+bl5eHg 4P7+/v39/fT09PLy8u7u7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAaAA7AAAI/gCVCRxI sKDBgwgTKlzIsKHDhxAjKgwiqs2kSJEgQfqyp2PHLxoxTmojSpTEkyglBrGYcU+el3n09PEDSFKg mzclAfLTRw/MPV4gjTSZsmhRURchuXwUs88fSYIGubEiqyqAq1gBNLPiRlCgPz197tE4MojRswuD JHX5UiagQILcNMtKl26zu3etuBgUaKcePXv0QIo0iSjaw8raROKYh6nbuFbmVpVlpbKby4Mya858 eWrlrV0l/fECWDBhw4hPimoJUw9NQVa0Yg6kk6dPmD9xt/Xi52kgKG4GCRLtpTjZNmZTQ5yktLXT QFNDA+qJe2wkkgkrrmWrx4tv0X6M/gvFrnzh6uaO+wCKOhzs7TzWyUesyDom7z9//EAKOh51eYKK sdWWH1D15cd78J12GFJKufRXcfwNNtR/ANYXE006UfdSfBQq1lxM3fFHWFlojRBCCA5goMMK5y3V 1B879VGdUMlRqIxaG7kUmHEikVTjQyuAcGIGDmSQwQUYzPBAA1UIKJMfUCI4Vhs2EjTJKrWYwogp mXSxY0iTTLhQAC2ocKIDHGywgAwYWPDAm3AeIIVztr3E1FiFVSnQJLXc4ksxuujyiy6npNGFYBKK WRAzKZipAgkp8ACCAyLg0MClDcD5ppIUVNCFFDL1oSF8Qvn3nyi8+KIqMH8aQwwx/66EMQcoVQxG mI/KBEBCCCSo0MIPLJSJwA6YFvsmBlFkYgopUTxwgQ8XXGBBBRUA0QUXeJp6qi2r2rKLLcAU42qs WIRhR623YpdDNM4wQ0IOInggrwfFNoCDDl20wooqqaSCCil3SHCBBgQXnAGbFmCAgQMkBKDnLsMU 4wswvPCySy3DuLpJGFiY4YodX6RrUhnOIFDDvPNeqkkXfKzCyssv8+svwM5uYPPNONusAZszEEEE GoooQsfQdRRdxyJII83I0ow04nQjjkTtCB5cVN3KMBEXA8wuFbMC6Cu5jIJFLsG4oonIQeQQQw4o a5KsI6moogrMMMvt77+kCPzB3v589+03BxdQ0IFyotyCdTFap7I1K7Z4YskmcIwSTC+9KMHGSD6S 0AIJHkRxByekkIJKv3LPXbfMeOddgQmst+466xoAIUEEEUzAQNBD02H00UkvwnTTT0s9ddV4ZPEK 1hH/qTUnlyDyRi659BJMMLiEgrkoQSwTAjMefPIJ6KKPHnfppfeLCt6cCDFDmjT8AMP7MJywwQW0 1187Aco5osUYyGNtjC+ccFwhzuCK6U0OF2uoQht8FAMEoMADnfge+M7Xrwpa8HyhI0X6JGCwDGhg fvYLoe1wRzSj9c53THsa1KRGNS6oYQxZ0AXyjKGLUlzCEoeIQxjIRjnKTYESC/7EnjJyYAIRRMF7 4Auf+Cp4vtRxghNOiEAHjxTC+k3gfsp5ghPSAIqMBeoUlkjEIeYgBzjwEBdonEIOgmgWSDlgC0h8 YgabSEcncuITUZQBwYxERftRYAIToEDtbie0EhbthL9TofBa6IT9jeEVgQpUJcZoCDEUcHqUw8UU ysBGZZQgBAvAgSfimMQMmjJ0T/SeGiKgRw3w8QKz+2Mgp/UALKamC1FYwha1AElJzkEMYiDb5HqB wE2SRIjR0MEIGoCJUUqwlKd84h0/4QlMRKACezQSLAM5A2pR6wF/JGTudofIFAaPhVW7AxWooIX9 ZSELv4hnJYA5CjQScw1rUP/jMQeCgA/gQA2ecOYzpUnQaVKzmtfM5pEkMIFpebMCtZwA/lJTBR88 YQlRcIITQBHPeNrhCEcwQhPQmM8EALEkAwnBDTBAhWYG1HukTCVMD4oJTBDBAgrNAEOnZYE/vomh 4jQk75KWyHNGrYWO0KUT1tlOWnRUCUdQQhOaoIQ12GEKsVCgEAVSAge88RIufelMxxrQal7iEkLg oCv5uFOffvOPE0XMMvjggy74IAoZ3UI8aYEEJUh1CkoggxIOUIbCbFUZyczADM4K1rI69rHVxARj kyDFtRppp9OawR8pAFQS6s6EvSuq0xZZNS444gkZ1SgVQkELWvjMr1QlQgT+pgALG+yTIDrgwAPo wFiwhtWxNZUsYxVBWYX6YAYT0CwgHwDRB0i0PNGoghTsCoQoaEIYQhCCz7ZLhCYoIAdD+ZEyQqAB C4xBEb09a3Brmt5LBE0RWYiAB/mo2EBSoJvfdG5QP3vI0JpztOgsLR8y8QTU4jUK2U2wEIagBAWU AQy3JcgIUqSF97b3wu9VhCXQwErLKpYCDvXmmygQV+UEQLpScKUPfACEFjuBCGuAhQ4gXBLxIjZa QrBEhtGL3rPyOMOWCHIiOkxfCzT0oc2lwH7J6d+lKTLAVfPIdAu8hCUAwQlCIIMBikAJCEeYIMm4 gAxmkIggB3nHOzazJcb+QIXZ6bHIIPZmT0FMYj2RyUw50EEZRIAASnzheoctSJEekIgyq/nQalaE E2QXAYHlFANx1iyILYDcJYOWqP9d4VFLi62PgEQkGAl1mI5p44HcYMxoQISqC21oIYcxDUuowOwk IAMOTDEDGAAnBR5gARyAE5Al1pMytIM5UiuEBxWwQBIOoepmO1sRd/BBBWgnMGo9a758xECmcOBr QE5Av55lMqadbNThldYjX/h0qEVyvVIDiFpEOIS85b3qOjBBBrODgL4foCZoWVsG2cZAt5fL7ToL WyAVWeAxA42QScjgAkQoRCHmrYhGgDAC+s54AjbAAQ4s4GDeFHOuvf3/ABwMQBgiUHK4L620TJP2 3J7WSEhG1MmJRKILsJzDxBfxhfLWL+MZn4AGOm5rgj2cWrJ8wAB2sAMRFEMYBtcTRUpCdXcbZDV8 sIAExoAHHuA7At2sYv3Q5PEOQmvXTE/7DlCu8kLyd6gtJzeANw3zPaRb5uwOIkoV0gY2SNsCgG+0 DFJwJFhWMbkDK7qHRcD4xjMeBxMoQAGEHYSpWz0hPlhANHxggWtyYBnMQAYIKvBwCZj+9GCHqAUc kFMdOF4EOzBAAXoA2JX3d9zAm7u5oxxzW4164doaiAM0rwwU0IAHz4hGAEDfAjH74PTQn4G0EpAA Z9HX9Y03wAEKcIAB/oDAYQc/CQkcEIBoPAMGzoDBM2KwfGa0QAMXOBLg5y8B6V/gAVNowhQogIEV 61kEDXAAPdADTVAJaKBjtgd3KCR3mrZ7nWZ36kZzx0QIV5AQGNAC5Xd+x6B+7Md8KYBN0oZkziIt E4AAKTAACtBQ8ZIA3NcBKrAMMRB+RfEAzLAM0aAMz/ACLwANyrcMyNACKXABCwA40VKEFPBwRtYE cjAHhmAEU5AAAzgFYjAHrHZmCVhODPhyvAeBtkJzNUYIs5AQNLgM5VeBV9CDoQeEIZABICADbviG FBAtRqYAzCAQAVACOSAACFACMngYFqACNRgAgiiIy+CDLQCEJCAD/yWgAV7ViHF4ATOQAFMABxI3 cWM0B6tWhQjoduIWd7nXgC20hXfHbkOBPRSYECFgAchQg4VYiMyQhikAAjdwAStgAydyIm1yARVA AQXQASvQhzYSAA2AAav4iq/4g0AYiyRwATRQAiqgAggwAxYgA7t4AAcQAjcIjBTSAgYwAySADOB4 iMkoi7uCAQuQJBYgZj3FfQOwDNpYJSnQAROAAZozjuS4AAsAfzLgAGzyACzYfXX4jlVSAmVAfQ+w MCRgAyRAAvhIMCmCXNtXAAYQAu4okHryAzaAARNgjQYJJxNAfRF5AAaQAy2QjRYpdWBQBV2QawrA gpLHfQpgAA1ggiMrYJInKWxIsRhfUAU82ZMj0Iwr8AM3qY3E9ntVV3lDWSUBAQA7 --dwgjtarlvecb Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <tbhawse> R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St 3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7 zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza BxcFCjgwgQSJCQcWCggIADs= --dwgjtarlvecb-- --qpuakeaagt Content-Type: application/x-compressed; name="stf.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment --qpuakeaagt-- Tag: Parrel Port Printer Tag: 41905
 - 12
 - eshell.exe where did it go? Back in the CE 3.0 days there was a nice little gui program for downloading images via Ethernet to a device. Great for production as they did not have to load the full PB. I see it is gone as of 4.0. Why? Is the source still out there somewhere? DV Tag: Parrel Port Printer Tag: 41901
 - 13
 - Newbie help requested Hello all, I've been experimenting with PB 4.2 with a fair amount of success. I built the CEPC, and ran through the tutorials just fine. I've used both eboot.bin to transfer the image via Ethernet, and copied the nk.bin to the drive and loaded it locally. I'm now trying to venture into new waters. I want to try and get a Fujitsu Stylus 1000 Pen tablet (486 DX 100, 340 Type III drive, 24 Meg RAM) running on CE. I've run into problems (surprise, surprise), and am looking for some insight. I've copied the CEPC nk.bin to the hard drive of the tablet, and select the load it locally option. I've been able to get Win95 and Win98 running on the tablet with the pen working. Question #1 The VESA test utility comes back with "Number of valid FLAT driver modes: 0". Does that mean that I cannot use this device at all, or I need to get/develop a custom driver for the adapter (Chips Technologies Question #2 When the image unpacks, it gets to the 100% mark, displays "Jumping to 0x0023AF88" and then reboots. I've looked at the debug info in Hyperterminal, but a good portion of it doesn't make sense to me. Can someone assist in decyphering it for me. I built 3 different CEPC platforms, Mobile Handheld, Mobile Handheld with lots of stuff removed, and the Tiny Kernel. I'm including the debug infor for each. Mobile Handheld: Debug Serial Init SysInit: GDTBase=814580f8 IDTBase=81486160 KData=81499800 Windows CE Kernel for i486 Built on Mar 13 2003 at 22:43:26 g_PageDir = 814a1000 No PCI bus +OEMKitlInit Unable to initialize KITL Transports! -OEMKitlInit KITL Initialization Failed, No debugging support available CEPC Firmware Init RTC - Status Reg B - 0x02 PCIBIOS:: BIOS Address static map to addr=a00e0000 GetPicRoutingIrqTable: Start search_pci_bios start search_pci_bios end fails GetPicRoutingIrqTable: FAILS!!! Firmware Init Done. Looking for rom chain Rom chain NOT found Booting Windows CE version 4.20 for (x86 ) &pTOC = 80225408, pTOC = 814562d8, pTOC->ulRamFree = 814a1000, MemForPT = 000240 00 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 1849, Secondary pages: 0, Filesystem pages = 924 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 814c6000, extension: 00001000, length: 00739000 X86Init done, OEMAddressTable = 8023afa8. Windows CE KernelInit Tiny Kernel: Debug Serial Init SysInit: GDTBase=802be0f8 IDTBase=802c2c40 KData=802cd8000t: 1089, SrcAddr.wPort: 2048 Windows CE Kernel for i486 Built on Mar 13 2003 at 22:43:26FTP link[1]: State:3, DestAddr.wPort: 1103, SrcAddr.wPort: g_PageDir = 802d5000 CEPC Firmware Init RTC - Status Reg B - 0x02 PCIBIOS:: BIOS Address static map to addr=a00e0000 GetPicRoutingIrqTable: Start search_pci_bios start search_pci_bios end fails GetPicRoutingIrqTable: FAILS!!! Firmware Init Done. Looking for rom chain Rom chain NOT found Booting Windows CE version 4.20 for (x86 ) &pTOC = 80225410, pTOC = 80281c40, pTOC->ulRamFree = 802d5000, MemForPT = 000240 00 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 6404, Secondary pages: 0, Filesystem pages = 3202 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 802fa000, extension: 00002000, length: 01904000 X86Init done, OEMAddressTable = 802327f8. Windows CE KernelInit Thanks in advance, -Jorden -- There are 10 different types of people in the world... those who understand Binary, and those who don't. Remove "nospam." to reply via email. Tag: Parrel Port Printer Tag: 41900
 - 14
 - Creating an image with keyboard and mouse to DBPXA250 I'm having some troubles with the keyboard and the mouse (both PS2). i created an image including the driver SA11x1 for keyboard and mouse common. But when i load the image on cotulla, jst appear the pointer and i can't use any of them.... Did someone have the same problem? Thanx for the help. Ps. I'm using winxp and plataform builder 4.1 Tag: Parrel Port Printer Tag: 41897
 - 15
 - About RDP Printer Hi, all: System: CE.net RDP5.1 I add the RDP printer in the control panel, then I connect to the Windows2000. I can use the printer in the client to print something. But if I shutdown the terminal then power on. I connect to the Windows2000 and try to print something. It will give me some error message like that " can't print to the port TS001". At this time, I have to log off and re-add the printer in the control panel, then I can use the printer? How to deal with it? All your answers will be highly appreciate! Thanks all! Tag: Parrel Port Printer Tag: 41891
 - 16
 - memory fragmentation Hi: Does anyone have perfomance benchmark information about the memory fragmentaion in CE.NET? That means when application allocated a lots of random size blocks and release randomly, over a certain period. We want to know how bad to cause CE.NET performance? Some one claimed, "Dynamic allocation was killer" in embedded realtime system? Is it true if the device had large enough memory, like 64MB or event 128MB in CE.NET device? We known that it is a serious factor in old-time when the device did not have large memeory. But now we are talking over 64MB device. So how the paging influence the performance in CE.NET? Does anyone known what kind of algorithm used on CE.NET for memory allocation, best-to-fit or some one else? Thanks Tag: Parrel Port Printer Tag: 41883
 - 17
 - Intel 82559 Ethernet using DMA We're building a CE.NET 4.2 image and including the Intel 82559ER ethernet driver (on a Geode based platform). Everything functions correctly, but our data transfer rate is slow (we've seen 2X performance when running Linux on the same platform). One thought is that DMA may not be properly enabled (can anyone describe precisely how to verify/correct this?). Another thought is that the port is somehow being shared as a debug port (which is not required), or that the interrupt is being shared with a display driver (but we use only a flat display). Any thoughts on the subject would be appreciated. Thanks, Kevin Tag: Parrel Port Printer Tag: 41880
 - 18
 - default web page Hi, I am trying to display my asp page when i type in the web address of my device. If i call my page default.htm, than it is displayed but if i change it to env.asp it comes up with an error message. I am using the registry settings below and i have got env.asp set as the default page. [HKEY_LOCAL_MACHINE\Comm\HTTPD] ;"DefaultDir"="\\" "IsEnabled"=dword:1 DefaultPage="env.asp;" [HKEY_LOCAL_MACHINE\Comm\HTTPD\VROOTS\/] "(default)"="\\windows\\www" "a"=dword:0 what could be going wrong? regards feroz Tag: Parrel Port Printer Tag: 41878
 - 19
 - waveOutMessage problems in 4.2 Hi, I am trying to pass a message from a user app to my MDD/PDD style audio driver using waveOutMessage in Win CE 4.2. I have tried various message ids (100+) but all I ever receive back is MMSYSERR_NOTSUPPORTED. Tracking the problem using debug zones and various debug output, it seems that the user message gets as far as WAVEAPI.DLL and no further, so my driver never sees the message. Is there something I need to do to get the message to be passed down to my driver? Jezz. Tag: Parrel Port Printer Tag: 41876
 - 20
 - Debugging PreFetchAbort and First Chance Exception 0xC000001C In the process of trying to get a driver (object form only, no source) running on my ARMV4-based platform, I get a "First Chance Exception 0xC000001C, Invalid System Service" window pop-up. When I click "ok" on the pop-up, the debugger stops at a DEBUGCHK(0) on line 1167 of the objdisp.c file, in the ObjectCall function. The stack at this point is full of PreFetchAbort entries. When I posted about this a month ago, Andrew Pearson said I might have a cache clearing problem, but our platform is simply using the pbuilder-supplied version (presumably in public\common\oak\csp\arm\sa11x0\cfw.c), as opposed to providing our own. The rest of our application and drivers and code which run on this same platform never run into this error, so I'm hesitant to think it is a cacheFlush issue. Any suggestions on what to try to figure this out? Not quite sure how to explain the PreFetchAborts in the stack, but another possibility is that the driver is trying to call a method in coredll.dll which isn't there. I have looked in the coredll.def to try to determine if the methods the driver dll needs (determined with the use of dumpbin) are there, but am having trouble sorting through all the conditionals there to determine if each item is actually in the final dll. Is there some easy way to look at the coredll.dll in the release directory to determine exactly which methods are really included there, since a dumpbin /exports on it seems to indicate that everything is included, which I think is incorrect? Arthur McNair Tag: Parrel Port Printer Tag: 41875
 - 21
 - Remote tools pb 4.1 Hi, I have a strange behavior with the remote tools in pb 4.1 When I download a debug image and start the kernel tracker all works fine until I want to save the collected data to a file. The 'save as..' dialog comes up, but when i want to enter a filename the kernel tracker close itself. Then when i restart the kernel tracker, i dont get a connection cause my system (the ce-device) hangs. Has anybody an idea ? Thanks Sebastian Tag: Parrel Port Printer Tag: 41873
 - 22
 - Application debugging using KITL Hi everyone, I'd like to get application debugging going with KITL if I can. First of all, how do i start up KITL when it's set up as PASSIVE kitl? Is there a program I can call to trigger the KitlInit function? Secondly, using active KITL i'm able to download the application and launch it from EVC++4.0. As soon as CEMON is launched though, it seems to cause an exception in coredll... has anyone been able to get this going or come across this before. Thanks, Glenn. Tag: Parrel Port Printer Tag: 41870
 - 23
 - SDK. BSP hi, if i wanna integrate my SDK(source code) with a specific BSP how can i go abt it... are there any issues related to it.. thank u ali Tag: Parrel Port Printer Tag: 41868
 - 24
 - TCL for CE.NET 4.1 Hi all, Does anyone know where I can find a solution for TCL on CE.NET 4.1? I found a TCLCE project on sourceforge, but it is only for CE 3.0, and there's no source code there. Thanks in advance! Jack Tag: Parrel Port Printer Tag: 41867
 - 25
 - PB Catalog Problem Hi everyone, I created a project in Platform Builder using the following BSP :"DBPXA250 Dev:Platform:ARMV4I". Now in the Catalog view, If I try to add components under the same BSP, I can't because they are all shadded out..what gives? PS I did make sure I had the right BSP. Thanks for your help. Tag: Parrel Port Printer Tag: 41855

Dear All,

I have a Wince.NET box. I would like to set this box as printer server.
Hence, I have added
1. Parallel Port Support
2. Printer Redirection
3. Serial and Parallel Redirection
4. Print Server

Also, I added some code in Platform.reg as following:
IF BSP_NOPARALLEL !

; Parallel Port Driver

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Parallel]

"DeviceArrayIndex"=dword:0

"Prefix"="LPT"

"Dll"="Parallel.Dll"

"Order"=dword:0

"IoBase"=dword:378

"IoLen"=dword:C

"SysIntr"=dword:17 ; SYSINTR_FIRMWARE + irq (IRQ5 for LPT2, IRQ7
for LPT1)

"DeviceType"=dword:0

"FriendlyName"=LOC_FRIENDLYNAME_PARALLEL

"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00, 00,4B,00,00,
00,00, 08, 00, 00, 00,00,00,00

ENDIF

And, I added some code in Platform.bib as following:

IF BSP_NOPARALLEL !

; Parallel Port Driver

parallel.dll $(_FLATRELEASEDIR)\parallel.dll NK SH

ENDIF

And, I added some code in Server.reg as following:

[HKEY_LOCAL_MACHINE\Services\Smbserver\Shares\Net_Printer]
"Enabled"=dword:1
"Type"=dword:1
"Path"="LPT1:"
"Driver"="Net_Printer"
"Comment"="Network Share Printer"

[HKEY_LOCAL_MACHINE\Services\Smbserver\Shares]
"NoSecurity"=dword:1

BUT, I still can NOT share my printer to the network, and PLUS, I DON'T KNOW
how to share the printer.

Can anybody give me some tips???

Thanks a million

Top