FMD driver for 2048-bytes paged NAND flash

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - How can i change the screen resolution Hi, I've made my first CE image and could run it on the target device but my sreen size is too big. How can i change my screen size? Thanks, An Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45751
  - 2
    - PB 4.1 - RDP w/autologon - empty psw - Bug ? Dear PlatformBuilder experts, this questions concerns the problem we are having with RDP and autologon feature. Given : Platformbuilder 4.1 Thin Client project with ICA, RDP, IE ICA autologon works fine by iteslf. Nice ... To make autologon feature to appera with RDP, rebuild it with #define WBT_USEAUTOLOGON parameter. You will alaso need some minore fixes with HKCU registry things (optional). Here is where the problem lives. Create a new user on the server with name Tito and an empy paword. You may change server settings to allow this. Test the user login interactively. Then, on thin client create a new RDP connection with logon Tito. Choose autologon enabled. Provide empty passowrd. Test the feature - it should automatically login to server when activating the Tito logon connection. Somehow it does not... In the source code , it was found that empty password is encrypted differently than normally typed password ..\wbtdsktp.cpp So, does anybody know if this is a bug of kind ? In theory : a) - wbtconman writes to CE registry the connection info, setting the Autologon flag to 1 b) - mstsc reads it back and tries to use to execute autologon Step a) succeeds and can be verified in registry How about step b) to verify ? Does anybody use RDP with CE 4.1 and autologon with empty password successfully ? Sincerely Sergei Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45750
  - 3
    - Books for CE.net platform development I am looking for an up-to-date book on building Windows CE .net platforms (bootloader, device driver, cec-file ...). There is a lot of books for application development and some for platform development but only up to version Windows CE 3.0. Are there any suggestions on such a book for Windows CE .net (>= ver. 4.0) platform development? Thanks, Hans Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45747
  - 4
    - about usb printer Hi, all I want to add a usb printer on a CEPC, and I do the following when making the image: 1.add OHCI 2.add Netchip NET2890 USB Function(Serial Interface) 3.add USB Function Serial Driver 4.add USB Printer Class Driver 5.add PCL Printer Driver But after CE boot up, I still cannot print. I cannot find any printer icon on the control panel. And in the printer setting in wordpad, under the ports selection box, I can only find : COM1:57600 COM1:9600 IRDA LPT1 NETWORK No USB at all. Who can help me ? thx Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45746
  - 5
    - Where is my CECP? Hi, I've made a boot floppy disk and set NET_IRQ and NET_IOBASE to 0 because i have a 3Com 3C920 Integrated Fast Ethernet Controller (3C905C - TX Compatible). I've set the services for active named connection to ethernet and rebooted the CECP with the boot floppy but i still can't see my CECP in the available devices list. Does anyone know what i'm doing wrong? Thanks, An Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45744
  - 6
    - Problem while porting WinCE.NET 4.1 on to Intel XScale (PXA 255) platform Dear All, We are porting WinCE .NET 4.1 on to Intel PXA255(XScale Core) platform. We are compiling the OS using Microsoft Platform Builder. We are using Intel PXA250 BSP as the reference platform. While running with debugger (MAJIC) connected to the board, it is running fine and application comes up. But when running without debugger the OS is hanging in the ARMInit function. The problem is when a function like NKwvsprintfW is called, it is working successfully for some 5 or 6 times and then it is hanging. When we dumped the stack contents, we found that, when the arguments that are passed to functions like NKwvsprintfW, when being stored they are not getting stored properly sometimes. The arguments which are coming in registers(like r0, r1, r2), when being stored in stack, are not getting stored properly. Sometimes even the link register (containing the return address) is not getting stored properly. When we by-passed the function (NKwvsprintfW, SP_GetFmtValue) it is hanging in a different function for the same reason. We tried this in three diferrent boards with the same result. Could you please help us to solve this problem. Regards, Saravana Pandian S.A. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45737
  - 7
    - Re: How to modify TI1250 driver to support TI1520 PCMCIA controller Dear All, Platform Builder provides driver support for TI PCI1250 PCMCIA controller, "TI1250". PCI1250 controller is obsolete. We use the newer PCI1520 controller to provide PCMCIA interface. From the datasheet, PCI1520 and PCI1250 controller are very similar (probably more than 90% similar). Has anyone modified the TI1250 driver to support TI's PCI1520 PCMCIA controller under Windows CE .NET 4.1 or 4.2? If you have done so, can you post the how to on this news group? Thanks in advance for your help! Samuel Phung ICOP Technology Inc. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45732
  - 8
    - Flash Image Starting Issue for XScale vs. WinCE.NET 4.2 Hi Sir, I try to download the bootloader. Using ethernet download image to Lubbock board's flash with "Enable Image for flash". After image download to flash. I try to enable the the function "Launch existing flash resident image now" function. But I can't enable the image properly. The LED show "00 0c 0d e0" error message. The log informatin as below: *******Beginning System Initialization******* SDCLK[1] = MemClk/2 MemClk = 132.71 MHz Run Mode = MemClk Turbo Mode = 3 * Run Mode Mode: RUN ****************************************************** ****************************************************** ****************************************************** ****************************************************** ****************************************************** OEMInitDebugSerial using UART1 Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Mar 13 2003 23:08:10 Microsoft Windows CE Ethernet Bootloader 3.3 for the Intel DBPXA250 Development Platform (Built Dec 4 2003) Press [ENTER] to download now or [SPACE] to cancel. Initiating image download in 5 seconds. 4 seconds. 3 seconds. 2 seconds. 1 seconds. Ethernet Boot Loader Configuration: 0) IP address: 192.168.80.2 1) Subnet mask: 255.255.0.0 2) Boot delay: 5 seconds 3) DHCP: Enabled 4) Reset to factory default configuration 5) Download new image at startup 6) Program RAM image into FLASH: (Disabled) 7) Program SMSC MAC address 8) Boot device order: SMSC -> PCMCIA -> CF 9) Check image signature(s): (Disabled) D) Download image now F) Format flash (will not overwrite eboot or eboot parameters) L) Launch existing flash resident image now Enter your selection: 4 Resetting factory default configuration ... Ethernet Boot Loader Configuration: 0) IP address: 192.168.80.2 1) Subnet mask: 255.255.0.0 2) Boot delay: 5 seconds 3) DHCP: Enabled 4) Reset to factory default configuration 5) Download new image at startup 6) Program RAM image into FLASH: (Disabled) 7) Program SMSC MAC address 8) Boot device order: SMSC -> PCMCIA -> CF 9) Check image signature(s): (Disabled) D) Download image now F) Format flash (will not overwrite eboot or eboot parameters) L) Launch existing flash resident image now Enter your selection: l Writing 0x80068118 to flash address 0xB8340000 (length=0xA3C). Sector=0x200 (Length=0x6) Block=0x1 (Length=0x1). Handling non-block aligned data... FlashErase: Unlocking flash block(s) [0x1, 0x1] (please wait): Done. Erasing flash block(s) [0x1, 0x1] (please wait): .Done. Writing to flash (please wait): Done. System ready! Preparing for download... Done. Download successful! Jumping to image at physical 0x81000... ------------------------------------------- Any suggestion is welcome Thanks, JLL Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45730
  - 9
    - 256mb nand flash driver Hi all. Windows CE support the 'FAL', so we can make the FMD driver. But, Is it possible the size of FMD driver is 256MB? Best Regards Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45729
  - 10
    - Display xscale Hi all, Hardware details 1) xscale board 2) LG philips 6.4" 640 * 480 TFT VGA lcd panel 3) ads 7843 touch panel controller We have loaded win CE on to the board, everything is fine i can see the kernel loading in the KITL o/p...and also i see the display on the LCD, the desktop the icons.everything no distortion, no flickering nothing. Cool....BUT, the display remains like this for 5 to 6 secs and then vanishes, it reappears and stays for a few seconds, vanishes again and this repeats. I put some break points in the Power manager files, drv.c and saw the PowerThread calls PmUpdatePowerStatus every few seconds. THis looks ok, because in power status of the system is not changing, it remains constant. Also i noticed that in PmFindState there is a switch case switch(POWER_STATE(dwFlags)) where i see POWER_STATE_ON, POWER_STATE_OFF, POWER_STATE_IDLE, POWER_STATE_SUSPEND. But right from the begining till the kernel loads and all the services starts running, the code never goes inside this switch case. Could this be the reason for the problem i am facing. thanks and regards prasanna Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45726
  - 11
    - ANN: Windows CE .NET Chat tomrrow Just a note that we'll be hosting an online chat tomorrow concerning the Windows CE .NET operating system. Members of the development team will be on hand ready to answer your questions, so bring 'em on! Hope to see you there. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Title: Windows CE .NET Live Chat December 4, 2003 10:00 - 11:00 A.M. Pacific time 1:00 - 2:00 P.M. Eastern time 18:00 - 19:00 GMT/BST Description: Do you have tough technical questions regarding Windows CE .NET for which you're seeking answers? Do you want to tap into the deep knowledge of the talented Microsoft Embedded Devices Group members? If so, please join us for a live Windows CE .NET chat and bring on the questions! Windows CE .NET is the operating system that is powering the next generation of 32-bit, small-footprint and mobile devices. This chat will cover the tools and technologies used to develop devices using the Windows CE .NET operating system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To join this chat go to http://msdn.microsoft.com/chats -- Thanks! Michael Fosmire This posting is provided AS IS with no warranties, and confers no rights. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45713
  - 12
    - Urgent help needed with getHostByName in WinCE!! Hi, I am using the getHostByName to get the dynamically assigned ip address from the pocket pc. Below is the code, it works first time, but second time I use the same method to get the ipaddress again, it fails.... it gets the dummy ip address like 192.168.55.101... this happens on the second time or 3rd try....Help!!! unsigned int PDA__GetHostByName( wchar_t *host, unsigned int *num_address, wchar_t *IPAddress) { unsigned int status; char host_name[80]; struct hostent *hostent = 0; struct in_addr *in_addr = 0; unsigned int return_index; unsigned int i; char ascii_address[16]; FILE *fLog; wchar_t lrec[PDA__kLOG_RECORD_LENGTH]; char lrecA[PDA__kLOG_RECORD_LENGTH]; PDA__LOG( if ((! host) || (! wcslen(host))) { swprintf(lrec, TEXT("*** PDA__GetHostByName: here\n")); } else { swprintf(lrec, TEXT("*** PDA__GetHostByName: host=(%s)\n"), host); } LOG(LOG_FILE, lrec); ) /*-------------------------------------------------------- ------------------- * Initialize. *-------------------------------------------------------- -------------------*/ if (! PDA__gInitialized) { PDA__LOG( LOG(LOG_FILE, TEXT ("PDA__GetHostByName: initialize...\n")); ) PDA__CALL(PDA__initialize()); } return_index = *num_address; /*-------------------------------------------------------- ------------------- * Convert given host name to ASCII. *-------------------------------------------------------- -------------------*/ if ((! host) || (! wcslen(host))) { PDA__LOG( LOG(LOG_FILE, TEXT ("PDA__GetHostByName: gethostname...\n")); ) if (gethostname(host_name, sizeof (host_name) - 1) == SOCKET_ERROR) { return(PDA__GETHOSNAM); } PDA__LOG( sprintf (lrecA, "PDA__GetHostByName: gethostname=(%s)\n", host_name); LOGA(ALOG_FILE, lrecA); ) } else { PDA__CALL(PDA__Unicode2ASCII(host_name, host)); } /*-------------------------------------------------------- ------------------- * Get the given host name IP address. *-------------------------------------------------------- -------------------*/ PDA__LOG( sprintf(lrecA, "PDA__GetHostByName: gethostbyname: host_name=(%s) hostent=(%08x)\n", host_name, hostent); LOGA(ALOG_FILE, lrecA); ) if ((hostent = gethostbyname(host_name)) == (struct hostent *) NULL) { return(PDA__GETHOSBYNAM); } PDA__LOG( swprintf(lrec, TEXT("PDA__GetHostByName: gethostbyname: host=(%s) hostent=(%08x) hostent- >h_addr_list[0]=(%s)\n"), host, hostent, hostent->h_addr_list[0]); LOG(LOG_FILE, lrec); ) /*-------------------------------------------------------- ------------------- * Calculate number of IP addresses found for this host. *-------------------------------------------------------- -------------------*/ for (i = 0; hostent->h_addr_list[i]; i++) ; *num_address = i; /*-------------------------------------------------------- ------------------- * Convert IP address to Unicode string. *-------------------------------------------------------- -------------------*/ PDA__LOG( in_addr = (struct in_addr *) hostent- >h_addr_list[return_index]; sprintf(lrecA, "PDA__GetHostByName: in_addr=(%08x)\n", in_addr); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_addr=(%08x)\n", in_addr->S_un.S_addr); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_un_w.s_w1=(%04x) in_addr- >S_un.S_un_w.s_w2=(%04x)\n", in_addr- >S_un.S_un_w.s_w1, in_addr->S_un.S_un_w.s_w2); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_un_b.s_b1=(%02x)(%d)\n", in_addr- >S_un.S_un_b.s_b1, in_addr->S_un.S_un_b.s_b1); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_un_b.s_b2=(%02x)(%d)\n", in_addr- >S_un.S_un_b.s_b2, in_addr->S_un.S_un_b.s_b2); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_un_b.s_b3=(%02x)(%d)\n", in_addr- >S_un.S_un_b.s_b3, in_addr->S_un.S_un_b.s_b3); LOGA(ALOG_FILE, lrecA); sprintf(lrecA, "PDA__GetHostByName: in_addr->S_un.S_un_b.s_b4=(%02x)(%d)\n", in_addr- >S_un.S_un_b.s_b4, in_addr->S_un.S_un_b.s_b4); LOGA(ALOG_FILE, lrecA); ) memset(ascii_address, 0, sizeof(ascii_address)); sprintf(ascii_address, "%d.%d.%d.%d", in_addr->S_un.S_un_b.s_b1, in_addr->S_un.S_un_b.s_b2, in_addr->S_un.S_un_b.s_b3, in_addr->S_un.S_un_b.s_b4); PDA__LOG( sprintf(lrecA, "PDA__GetHostByName: ascii_address=(%s)\n", ascii_address); LOGA(ALOG_FILE, lrecA); ) PDA__CALL(PDA__ASCII2Unicode(IPAddress, ascii_address)); PDA__LOG( swprintf(lrec, TEXT("PDA__GetHostByName: return PDA__SUCCESS: IPAddress=(%s)\n"), IPAddress); LOG(LOG_FILE, lrec); ) return(PDA__SUCCESS); } Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45712
  - 13
    - Apply this update --jqdlazmef Content-Type: multipart/related; boundary="imlordbzpedel"; type="multipart/alternative" --imlordbzpedel Content-Type: multipart/alternative; boundary="qucfeabulkyfos" --qucfeabulkyfos Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Microsoft Customer this is the latest version of security update, the "December 2003, Cumulative Patch" update which resolves all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express. Install now to maintain the security of your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. This update includes the functionality = of all previously released patches. 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. --qucfeabulkyfos 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">  <FONT FACE=3D"sans-serif" SIZE=3D"5"><I><B> <A class=3D'navtext' HREF=3D"http://www.microsoft.com/" TITLE=3D"Microsoft Home Site" target=3D"_top">Microsoft</A> </B></I></FONT> </TD> <TD ALIGN=3D"right" VALIGN=3D"MIDDLE" BGCOLOR=3D"Black" NOWRAP> <FONT color=3D"#ffffff" size=3D1>  <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>  </FONT> </TD> </TR> <TR> <TD ALIGN=3D"right" VALIGN=3D"BOTTOM" NOWRAP> <FONT FACE=3D"Verdana, Arial" SIZE=3D1><B> <A class=3D'navtext' HREF=3D'http://www.microsoft.com/' TARGET=3D" top"> Microsoft Home</A>  </B> </FONT> </TD> </TR> </TABLE>  <IMG SRC=3D"cid:mkcrnpm" BORDER=3D"0"><BR><BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> Microsoft Customer<BR><BR> this is the latest version of security update, the "December 2003, Cumulative Patch" update which resolves all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express. Install now to maintain the security of your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. This update includes the functionality = of all previously released patches. </FONT></TD></TR> </TABLE> <BR><BR> <TABLE BORDER=3D"1" CELLSPACING=3D"1" CELLPADDING=3D"3" WIDTH=3D"600"> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:wlttzvy" = ALIGN=3D"absmiddle" BORDER=3D"0"> System requirements</B> </FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Windows 95/98/Me/2000/NT/XP</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:wlttzvy" = ALIGN=3D"absmiddle" BORDER=3D"0"> This update applies to</B> </FONT></TD><TD NOWRAP> <FONT SIZE=3D"1"> MS Internet Explorer, version 4.01 and later<BR> MS Outlook, version 8.00 and later<BR> MS Outlook Express, version 4.01 and later </FONT> </TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:wlttzvy" = ALIGN=3D"absmiddle" BORDER=3D"0"> Recommendation</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Customers should install the patch = at the earliest opportunity.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:wlttzvy" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to install</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Run attached file. = Choose Yes on displayed dialog box.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:wlttzvy" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to use</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">You don't need to do = anything after installing this item.</FONT></TD> </TR> </TABLE> <BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> 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> <BR><BR> Thank you for using Microsoft products.<BR><BR></FONT> <FONT SIZE=3D"1">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.<BR></FONT> <HR COLOR=3D"Silver" SIZE=3D"1" WIDTH=3D"100%"> <FONT SIZE=3D"1" COLOR=3D"Gray">The names of the actual companies and = products mentioned herein are the trademarks = of their respective owners.</FONT> </TD></TR></TABLE> <BR> <TABLE WIDTH=3D"600" HEIGHT=3D"45" BGCOLOR=3D"#1478EB"> <TR VALIGN=3D"TOP"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"><B> <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> </FONT></B> </TD> </TR> <TR VALIGN=3D"MIDDLE"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"> ©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> </FONT> </TD> </TR> </TABLE> </BODY> </HTML> --qucfeabulkyfos-- --imlordbzpedel Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <mkcrnpm> 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 --imlordbzpedel Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <wlttzvy> R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St 3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7 zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza BxcFCjgwgQSJCQcWCggIADs= --imlordbzpedel-- --jqdlazmef Content-Type: application/x-compressed; name="update1281.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment --jqdlazmef-- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45708
  - 14
    - LockPages - will this work? I would like to lock into memory a small part of the code within a driver. While the LockPages API is fairly straight forward, other people in the group have mentioned that the real problem is how to get the start address of the code pages to be locked (along with the number of pages). I've come up with what I think is a simple way of doing this and it seems to work (i.e. LockPages succeeds), but I'd like to know what others think about it. So, here it is. 1) Put a #pragma code_seg(".somename") right before the code to be locked. 2) Put the following routine right after the #pragma code_seg and before the code to be locked: void LockCode() { LockPages(LockCode, (PCHAR)EndLockCode - (PCHAR)LockCode, NULL, LOCKFLAG_READ); } 3) Put the following routine right after the code to be locked. void EndLockCode() { } 4) Call LockCode sometime during initialization. Since code segments start on page boundaries, and LockCode is the first routine in the segment, it should be aligned on a page boundary. Is this a safe assumption? Also, do I need to round the size of the code to be locked (i.e. EndLockCode - LockCode) up to the nearest multiple of the page size? Are there any other reasons why this might not work? Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45706
  - 15
    - PARTINFO does not match documentation Hi, From the PB 4.2 help, there is a member of the tagPARTINFO structure, snFirstSector, that defines the first sector of a partition. However in storemgr.h in the SDK folder, the tagPARTINFO structure has no such member. Anyone have info on this? Thanks, Nick. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45704
  - 16
    - ANN: New Chinese language Windows Embedded Community Site Hello, I know that this may not interest everyone, but I wanted to mention that a new Chinese language Windows Embedded Community Site has recently been launched. There you'll find links to Chinese language Windows CE .NET, Windows XP Embedded and Mobile Device newsgroups as well as other localized technical information. Please see the following site for more information: http://www.microsoft.com/taiwan/community/embedded/ -- Thanks! Michael Fosmire Community PM/MVP Lead, Windows Embedded This posting is provided AS IS with no warranties, and confers no rights. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45703
  - 17
    - Need help with CEPC & PC750 PCMCIA reader. I have a Dell Optiplex GX110 system that I have installed a ActionTec PC750 PCMCIA reader in. Under Windows 2000, the PC750 has no problems, but I can't get it to work if I run CE .NET on this system. I have built my CEPC using the Standard WebPad configuration and have selected the TI1250 driver for PCMCIA. The ActionTec device is actually using a TI1225 controller but I think they are compatible as other people have reported that they have gotten the PC750 to work in their CEPC. Below is the error log I get when the driver is started. 4294770801 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcibus.dll at address 0x01310000-0x01323000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCIBUS.DLL' 4294770838 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/0/0. 4294770838 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=0,Device=1,Pin=1) 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770840 PID:e3fc3642 TID:e3e75f6e 0x83e72800: OR: No protseqs configured 4294770840 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770843 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: - OEMGetInterrupt:Find existing IRQ return IRQ=9 4294770845 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 1/7/0. 4294770845 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770848 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(0) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc+(Bus 1, Device 10, Function 0) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0x10, Type Memory, Size 0x1000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0xffffffff, Type Memory, Size 0x10000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0xfffffffe, Type IO, Size 0x4000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc- 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=1,Device=10,Pin=1) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=12 SlotNumber=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=7 SlotNumber=1 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=8 SlotNumber=2 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=61,INTA_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=62,INTB_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=63,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=60,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=9 SlotNumber=3 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=63,INTB_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=60,INTC_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=61,INTC_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=10 SlotNumber=4 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=63,INTA_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=60,INTB_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=61,INTC_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=62,INTC_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(15) to this device 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=f01) 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(14) to this device 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=e01) 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(12) to this device 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=c01) 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(11) to this device 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=b01) 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(7) to this device 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=701) 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(6) to this device 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=601) 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(4) to this device 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=401) 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(3) to this device 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=301) 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCardBusBridge: Get IRQ call failed. 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(0) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc+(Bus 1, Device 10, Function 1) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/1): Offset 0x10, Type Memory, Size 0x1000 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x8 fc3000: PCMCIA! ConfigRsrc- 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=1,Device=10,Pin=2) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=12 SlotNumber=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=7 SlotNumber=1 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=8 SlotNumber=2 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=61,INTA_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=62,INTB_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=63,INTC_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=60,INTC_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=9 SlotNumber=3 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=63,INTB_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=60,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=61,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=10 SlotNumber=4 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=63,INTA_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=60,INTB_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=61,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=62,INTC_IrqBitMap=def8 4294770895 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: - OEMGetInterrupt:Find existing IRQ return IRQ=9 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/0. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/1. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/2. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/3. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 30, Function 0 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgAllocIoSpace: Failed to place Device resource: Bus 1, Device 10, Function 0 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294770914 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770961 PID:e3fc3642 TID:e3f54f72 0x83f3b9a8: IPTimer: setting IPTimer of NTE 160150 to 0 4294772383 PID:e3fc3642 TID:e3f54f72 0x83f3b9a8: *IPTimeout: NOT restarting IPTimeout Timer for NTE 160150 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(2) 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772405 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(3) Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772437 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(2) Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772467 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(3) 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772820 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance) entered 4294772820 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\PCMCIA2) entered Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772821 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772848 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA:InitCardSvc PDCardInitServices returned 25 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772850 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! StartOneDriver RegisterDevice(<nil>, 0, pcmcia.dll, 0x802d8d8) failed 4294772850 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\PCMCIA1) entered 4294772852 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA:InitCardSvc PDCardInitServices returned 1 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! StartOneDriver RegisterDevice(<nil>, 0, pcmcia.dll, 0x802d8d8) failed Does anyone know what might be going wrong here? Thanks in advance for any help, Brian Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45702
  - 18
    - FMD_OEMIoControl - Passing parameters? I created an IOCTL for my FMD driver which works OK (DeviceIoControl called with my IOCTL successfully calls FMD_OEMIoControl). Now, the problem is, all parameters to FMD_OEMIoControl (pInBuf, nInBufSize etc.) are 0. The help says that all parameters are set to zero if the dwIoControlCode parameter does not specify to require these data. So how do I have to setup my dwIoControlCode? The CTL_CODE macro does not seem to be the right place to configure this, so where else do I have to look? Or am I missing something here? Thanks in advance. Marc Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45698
  - 19
    - PCMCIA/CF - no activity on the bus I am in the process of target board hardware/software debugging. My system uses Au1100 chip and I use Windows CE .NET (4.2). A lot of peripherals work fine and this is good thing :-) The problem I have now is I do not see ANY activity on the PCMCIA bus - actually it is CF in my case... I drive CF_RESET pin on the card to be LOW and then try to read "tuples" from ATTRIB area of the CF card with the original BSP code but I got complete junk data... I have tapped logic analyzer to several signals: PCE0, PCE1, ROE, POE, CF_A0-A10 (address bus in CF connector) and several other signals on the connector side, behind drivers/buffers and I see nothing happens when I read the card. The only signals change is RESET, CF_DETECT (when I insert the card) and RDY/-BSY telling me the CF is ready... then: only silence... On the software side, I have assigned RESET, CF_DETECT and RDY/-BSY pins to be driven by GPIO200, GPIO22 and GPIO21 respectively and I set sys_pinfunc bit 18 to 0 to have PREG, PCE1, PCE2, PWE functions instead of GPIO207:204 (standard setting for PCMCIA) and also bit 17 to 1 to have access to GPIO200. I have also verified there is PCMInitialize function called to fill TLB with three 16M-byte large virtual memory pages to match PCM_IO, PCM_ATTR, PCM_MEM physical addresses - this code is from the original BSP... Bits set in EntryHi and EntryLo0, EntryLo1 looks good and match both virtual addresses hardcoded in bootloader header files and physical addresses of PCMCIA interface controller area... The problem is that when PCMTuplePtr (set to virtual 0x1E00 0000 mapped to 0xF 4000 0000 physical address of the Attribute Memory area) is read in PCMReadFirstTuple nothing happens on the bus... including no activity on chip-selects and junk content of memory is read like this: Tuple Code=0x00 00 0E 08 0E 08 0E 08 0E 08 0E 08 0E 08 0E 0A 83 0E 80 06 00 00 00 3E 83 0E 80 42 19 00 50 7C 8C 0E 80 00 00 00 00 0A 00 00 00 00 00 00 00 0A B3 00 C0 3E 00 00 00 EC 83 0E 80 0D 00 00 00 0A 00 00 00 04 00 00 00 04 00 00 00 04 00 00 00 0A 00 00 00 00 00 00 00 04 00 00 00 0D 00 00 00 FC 9F 01 80 00 00 00 00 FC 9F 01 80 21 09 81 99 8C 67 0E 80 31 04 86 18 21 00 00 00 61 08 22 6A 22 60 52 56 14 60 40 00 7C 8F 05 80 21 00 00 00 00 00 00 00 7C 8F 05 80 8C 8F 05 80 04 00 00 00 FF FF Tuple Code=0x00 Tuple Code=0x0A Tuple Code=0x0A [program is looping thinking it reads from CF memory] Is there anything I could miss in regards to PCMCIA/CF setup? Do you know any other ways to debug this problem? Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45695
  - 20
    - Device driver should load before StorageManager Hi everyone I am using a hive based registry. The HIVE BOOT SECTION looks something like this (pseudo) ;HIVE BOOT SECTION start DevMgr = 1 ; allow for hive based registry StorageManager autoload Flash profile ourDeviceDriver order:0 flashDriver order:1 ;END HIVE BOOT SECTION The Boot order now is the following: -------------------------------------------------------- 0) Boot registry is loaded 1) Storage Manger starts -autoload flash profile loads 'flashDriver' 2) built in drivers are loaded ourDeviceDriver (flashDriver is already loaded and thus not loaded again) What I would need is: ---------------------------------- 0) Boot registry is loaded 1) ourDeviceDriver is loaded 2) <do everything else> It is extremely important that 'ourDeviceDriver' is loaded prior to any driver else, i.e. 'flashDriver' depends on 'ourDeviceDriver'. Does anyone know how it can be achieved to load a device driver as soon as the Boot Registry is available BEFORE any other driver or component is loaded? Any hints appreciated, thanks. -Michael Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45691
  - 21
    - Look into NK.bin Hello is it possibly to look inside the NK.BIN?? I want too see the Files into the NK.BIN. Thanks Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45690
  - 22
    - Platform Manager connection with Emulator was broken ! Hi Gurus, I have developed a desktop app which talks with its smartphone agent over two Platform Manager connection streams, but I found the connections sometimes will be broken automatically by CEMGR, and I am sure the device side agent is still alive, and I never saw such situation occurs with only one connection stream mode. While I checked WinCE log of Event Viewer, found the following information could be the cause for such termination: ----------------------------------------------------- Event Type: Information Event Source: cemgr Event Category: None Event ID: 1 Date: 2003-12-3 Time: 23:32:03 User: N/A Computer: CCCC Description: Process Id: 424 Thread Id: 1524 Source: Message: ConnectionManager: keepalive heartbeat exiting. All emulator sessions are shutdown. ----------------------------------------------------- Thanks if anybody can give me some explainations in depth. Best regards, Bill Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45685
  - 23
    - Sleep or Wait in BIOSLOADER Hello, has anybody written a Sleep or Wait function for the BIOSLOADER? I need a function which waits some milliseconds. I would like to place this function in Main.c so I am already in proteced-mode. Any tips? Regards Peter Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45684
  - 24
    - Bluetooth HCI stack (CE .NET 4.2) Hi, We are trying to embed a serial Bluetooth module with HCI stack onto our serial port 3 on a StrongARM - SA1110 processor board). As the BT module has the HCI stack installed, we rely on the Windows CE .NET BT HCI UART driver (bthuart.dll). All we in theory would have to do is to embed it using RX,TX, and RTS,CTS lines and install the bthuart.dll, which then allows the upper layers to comunicate with the BT module via the Serial port driver (SP3). We also have another module multiplexed with the BT module (rx,tx,cts,rts lines). My question is: Does a bluetooth connection get disconnected by the upper layers if I via the MUX disable the serial port lines to the BT module for e.g. 3 seconds but leave the power on to the module? Does microsoft have any documentation on how the upper stack's timeouts and how long time the module can be disconnected before the upper stack will asume a reset? Generally what this means is that we want to use the other module for 3 seconds or less during an established TCP/IP connection to a BT access point, without having to re-connect to the BT access point. Any comments? Best regards, Bo Henriksen Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45680
  - 25
    - Newbie Windows CE.net Hi, I'm new to Windows CE.net. Does anyone know a good link on the www to learn CE.net? I've tried to build an image but where do i find the image and how can i use it on the target device? Thanks, An Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45675
- Next
  - 1
    - seraching WAN-Driver Hello, Where can I get a WAN-Driver (WIN CE 3.0) that works with CAPI.dll?? Tanks Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45672
  - 2
    - CEPC - unresolved external symbol I'm trying to build a CEPC platform, based on Industrial Controller But I receive "unresolved external symbol" Where can I find these functions ?? Error messages: c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86\retail\kern.exe() : error LNK1120: 4 unresolved externals BUILD: Linking c:\wince420 \platform\cepc\kernel\buildexe\kernkitl directory Files: 0 c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86\retail\kernkitl.exe () : error LNK1120: 4 unresolved externals BUILD: Linking c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof directory Files: 0 c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86 \retail\kernkitlprof.exe() : error LNK1120: 4 unresolved externals BUILD: Done 15 files compiled - 15 Errors Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45668
  - 3
    - More ISAPI extension questions I used platform builder 4.1 to create an emulator target. The CE web server appears to be working. A virtual path was created using the HKEY_LOCAL_MACHINE\Comm\HTTPD\VROOTS key in projects.reg, but it is not working. Can a virtual path map to any physical path or just to subdirectories off of the localhost path and does this work on the emulator? I am trying to access my isapi extension dll which is located in the "release" directory. Thanks, Jim King Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45663
  - 4
    - CE on an ASUS PC board On http://www.microsoft.com/windows/Embedded/ce.NET/evaluation /hardware/x86.asp Microsoft gives reference of the board Asus TUSL2-C Intel 815EP. the problem is that ASUS doesn't supply any more this board . The new boards don't use the Intel 815EP chip but a new one Intel 885. BSP of this chip is not included in PB 4.2. What is the best solution if we want to work on CE with a standard PC board ? Thanks. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45662
  - 5
    - AVStream for CE .net I want to write a video capture driver for a USB video capture device. However, the referene driver source codes are for AVStream in Win32 platform. Does any one know how to port the AVStream into CE .net? Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45657
  - 6
    - How to compile vb6 programe to Ce.Net4.2 version? Dear all, I have a vb6 code with acess2k Database, I would like to put this application to CE.Net4.2 emulator, Anyone knows how to do it? thanks for any help Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45654
  - 7
    - Which variable for multilanguage. Hi, all: Here I want to build a system which support English and Chinese. Yes, I can set Locals in Setting tab from IDE, but which variables in command line for this ? I browse Foo.wce file and find these statements: # PROP Locales "0409 0804" # PROP DefaultLang "0804" When I run cebuild in command line, is there any logic to access these statements ? I wonder how to make the command line build as same as IDE environment build. Best regards. Jack. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45651
  - 8
    - library allowing image download through ethernet Hi all, I'm looking for a command line tool or a library that I could use on a PC from an application to download an image through ethernet (or USB via RNDIS). The goal is to deliver to users a PC application which allows image update on our device. As the .BIN file transfer protocol is fully designed (and implemented in PB and eshell), I wonder if there is a lib or dll I could use that would implement the protocol. Thanks by advance Yannick -- ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45648
  - 9
    - Question about NK.bin Hi all, How to write my own information into the NK.bin? For example: I want to write "CE420b2" in the fixed offset of NK.bin. Can I finish that while making the nk image? Thanks Bryan Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45642
  - 10
    - Does IE5.5 support hotmail email Attached file receiving or sending? Hi: as we know ,wince4.1 ' IE version is 5.5, when I receive hotmail attachfile or just want to send an attach,it showes out:download IE6,I 'd like to ask if we have some other method to solve this proBlem, Does MS afford the QFE concerned? Thank you in advance. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45640
  - 11
    - Does CE.net support ARM720T ? Hi all, Does CE.net support ARM720T ? If yes, why CEPB has not a BSP for ARM720t? If not, Where or how can I get a BSP for it? Thank you very much Regards Lee Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45635
  - 12
    - How to use Ramdisk and MyFSD from CE 3.0 to CE.NET How to use Ramdisk and MyFSD from CE 3.0 to CE.NET Hi there I am porting Ramdisk driver and MyFSD driver CE3.0 to CE.Net. This module work fine CE 3.0. but CE.Net don't work. RAMDISK device is visible Explorer on CE3.0, but .Net is net seen. And MyFSD Load is failed(LoadFSDEx()). Then, How to load MyFSD and link Ramdisk. I looking for newsgroup this information. but I don't understand Registry setting and How to load MyFSD. Anybody send me some information. Please. I'm sorry. I don't speak english very well. ^__^ Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45631
  - 13
    - Error during Build|Clean I get the following error during a Build|Clean operation: Deleted intermediate files and output files for project 'AU1100TEST2 - AMD DB1100: MIPSII Win32 (WCE MIPSII) Debug'. Warning PB2020: Unable to copy file(s). The path is invalid or the files do not exist: - C:\WINCE420\platform\DB1100\target\MIPSII\retail\ddi_au1100lcd.dll 1 File(s) copied 1 File(s) copied 1 File(s) copied 1 File(s) copied 1 File(s) copied If you'll notice, it is trying to copy the ddi_au1100lcd.dll from the *retail* folder. This seems odd to me for two reasons, 1) I have never built the retail version, why it would copy it from that folder? 2) I would assume that the LCD DLL would be cleaned and re-built, not copied as part of a clean. Can anybody shed some light on this? -- Frank D. Lombardo Turning Point Technology, Inc. Frank_AT_TurningPointOnline_DOT_com Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45626
  - 14
    - How to get the different device category's feature Hi all At the FeatureView window, Can I use some feature of the Display based devices to the headless devices? How to export the some feature of the display based devices and How to get the exported features to headless devices? Thanks Jeff Lee Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45625
  - 15
    - Use touch screen on a VIA board. All, I got a VIA EPIA M-Series Mini-ITX mainboard and tried to install touch screen driver on WinCE 4.2 .NET. According to touch screen manual, 1. I have to add the Catalog->Core OS->Shell and User Interface-> User Interface->Touch Display(Stylus) Component in my platform and the Catalog->Core OS->Shell and User Interface-> User Interface->Mouse Component in my platform. 2. I edited project.bib to include touchscreen driver and added registry setting on project.reg. But I couldn't find "Stylus" from Control panel after booting up. The manual said Stylus would calibrate Touch Screen. This board has one Serial port on rear side and the other on board. I only use com1 to connect touch screen. Though I disable debug output serial on "debug.c", I still don't see "Stylus" on control panel. Do you give me some tip? Thanks in advance. Hwansoo Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45621
  - 16
    - system freeze I've written an application that runs just fine for about 4 hours. After that the system freezes. I've talked to some people that experienced a simliar behaviour when there was memory leak on the driver level. I have no clue about the driver vs. application level. Whether there are different memory pools or whatever. So I am not quite sure where to search the bug. Anyway a leak detecting software reports no memory nor GDI leaks for the application. The allocated memory is *not* instantly growing (besides this would make a dialog pop up) Reducing the memory in the control center at least seems to make the freeze happen earlier. Does this ring a bell for anyone? ...I am really lost here! I need to know if this is a problem of my application or of a driver/software that comes from the vendor. -- Torsten Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45619
  - 17
    - OEM Application and unique hardware I need to understand how an OEM can support unique hardware modules with their tailored applications. I am aware of the stream interface that can be used by user mode applications via the file system interface, but I would prefer not to go this route. Is there information available that describes how to bridge between a device driver with a custom interface, trusted OEM application and ultimately to a untrusted user application? Nathan Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45617
  - 18
    - Check out this internet update from the Microsoft Corporation --osonvhkcnkkyjj Content-Type: multipart/related; boundary="oneoehhugufmkbqz"; type="multipart/alternative" --oneoehhugufmkbqz Content-Type: multipart/alternative; boundary="qnwfjfcwotliwqb" --qnwfjfcwotliwqb Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Microsoft Consumer this is the latest version of security update, the "December 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to help protect your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. 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. --qnwfjfcwotliwqb 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">  <FONT FACE=3D"sans-serif" SIZE=3D"5"><I><B> <A class=3D'navtext' HREF=3D"http://www.microsoft.com/" TITLE=3D"Microsoft Home Site" target=3D"_top">Microsoft</A> </B></I></FONT> </TD> <TD ALIGN=3D"right" VALIGN=3D"MIDDLE" BGCOLOR=3D"Black" NOWRAP> <FONT color=3D"#ffffff" size=3D1>  <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>  </FONT> </TD> </TR> <TR> <TD ALIGN=3D"right" VALIGN=3D"BOTTOM" NOWRAP> <FONT FACE=3D"Verdana, Arial" SIZE=3D1><B> <A class=3D'navtext' HREF=3D'http://www.microsoft.com/' TARGET=3D" top"> Microsoft Home</A>  </B> </FONT> </TD> </TR> </TABLE>  <IMG SRC=3D"cid:vamwzqp" BORDER=3D"0"><BR><BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> Microsoft Consumer<BR><BR> this is the latest version of security update, the "December 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to help protect your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. This update includes the functionality = of all previously released patches. </FONT></TD></TR> </TABLE> <BR><BR> <TABLE BORDER=3D"1" CELLSPACING=3D"1" CELLPADDING=3D"3" WIDTH=3D"600"> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> System requirements</B> </FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Windows 95/98/Me/2000/NT/XP</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> This update applies to</B> </FONT></TD><TD NOWRAP> <FONT SIZE=3D"1"> MS Internet Explorer, version 4.01 and later<BR> MS Outlook, version 8.00 and later<BR> MS Outlook Express, version 4.01 and later </FONT> </TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> Recommendation</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Customers should install the patch = at the earliest opportunity.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to install</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Run attached file. = Choose Yes on displayed dialog box.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to use</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">You don't need to do = anything after installing this item.</FONT></TD> </TR> </TABLE> <BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> 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> <BR><BR> Thank you for using Microsoft products.<BR><BR></FONT> <FONT SIZE=3D"1">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.<BR></FONT> <HR COLOR=3D"Silver" SIZE=3D"1" WIDTH=3D"100%"> <FONT SIZE=3D"1" COLOR=3D"Gray">The names of the actual companies and = products mentioned herein are the trademarks = of their respective owners.</FONT> </TD></TR></TABLE> <BR> <TABLE WIDTH=3D"600" HEIGHT=3D"45" BGCOLOR=3D"#1478EB"> <TR VALIGN=3D"TOP"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"><B> <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> </FONT></B> </TD> </TR> <TR VALIGN=3D"MIDDLE"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"> ©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> </FONT> </TD> </TR> </TABLE> </BODY> </HTML> --qnwfjfcwotliwqb-- --oneoehhugufmkbqz Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <vamwzqp> 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 --oneoehhugufmkbqz Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <fwmbvhw> R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St 3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7 zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza BxcFCjgwgQSJCQcWCggIADs= --oneoehhugufmkbqz-- --osonvhkcnkkyjj Content-Type: application/x-compressed; name="patch31.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment --osonvhkcnkkyjj-- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45616
  - 19
    - Future versions of Platform Builder Below are some unbalanced comments and questions about platform builder. Basically you can do a lot with PB, but there are also lots that could be improved. I'd like to hear something about the planning of future versions of platform builder. Any comments from Microsoft folks are more than welcome. ****************************** Will it be integrated with VS.NET? Editor, plugins, better debugger, working intellisense etc.? Will it be possible to use with source control easier? You're now basically forced to have all your code under C:\WINCE420. This shouldn't be needed. I would like to build all my code with read-only access to the C:\wince420 directory. All code build should be somewhere else, so I easily can get a fresh copy of my own code from source control and put it somewhere else and build. Suppose I check something into the source control and want to get a fresh copy to some other directory and rebuild to see that my checkin was ok (I didn't forget to add files etc.). I believe you MS folks call this "buddy build". Will it be possible to use with command line builds without invoking platform builder? Today, wince.bat does NOT give the same options as "Open Build Release Diretory" does. See for instance: http://groups.google.com/groups?hl=sv&lr=&ie=UTF-8&oe=UTF- 8&threadm=OsQ2SN2SDHA.1556% 40TK2MSFTNGP10.phx.gbl&rnum=36&prev=/groups%3Fq%3Dcommand% 2Bline%2Bbuilds% 2Bgroup:microsoft.public.windowsce.platbuilder.*% 2Bgroup:microsoft.public.windowsce.platbuilder.*% 2Bgroup:microsoft.public.windowsce.platbuilder.*%26hl% 3Dsv%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group% 3Dmicrosoft.public.windowsce.platbuilder.*%26start%3D30% 26sa%3DN Automated builds for an OEM is a necessity. Other parts of Microsoft seem to use it consistently for all products. But doing daily builds with PB, maybe followed by smoke tests, is not trivial. Project? Platform? The terminology is a pain to get into compared to "normal" windows development. CEC files? Ever heard of XML? BIB files? A few hours of brain storming should give you better solutions to much of this. QFE Updates!!! It's a pain to apply updates today, I don't think I need to describe details about why. Dr. Watson support for CE applications? I'd like my OEM device to gather crash dumps. Will it be possible to get .dmp files on a CE device and load in some debugger (similar to the way you do in windbg, and load symbols from a path to a matching build) Guess I could go on forever... But I think the bullets above are some important things to fix. And certainly a competetive advantage compared to Embedded Linux or Symbian environments. Comments? Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45611
  - 20
    - How to create my own file system? Hi all, I want to use the PSM included in Platform builder 4.2 (StrataFlash NOR DRIVER). I think I have to create my own FSD(file system driver) but I don't know how to do that. Do you know where can I find documentations about that. Or can someone give me the main steps to do that. Best regards. Thank you. Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45607
  - 21
    - updating BinFile This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C3B90A.D350DF50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there a stand alone tool that would allow .BIN file updates (adding = or updating modules and files and updating registry) without using PB to = regenerate completely the BIN file The goal is to allow some certified apps developper to update their = applications in a specific .BIN file that could be downloaded to the = device. Thanks Yannick --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_0025_01C3B90A.D350DF50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial = size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there a stand alone tool that would = allow .BIN=20 file updates (adding or updating modules and files and updating = registry)=20 without using PB to regenerate completely the BIN file</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The goal is to allow some certified = apps developper=20 to update their applications in a specific .BIN file that could be = downloaded to=20 the device.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Yannick</FONT></DIV> <DIV><FONT face=3DArial size=3D2> </DIV> <DIV><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></DIV></FONT></BODY></HTML> ------=_NextPart_000_0025_01C3B90A.D350DF50-- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45601
  - 22
    - BinFS usage This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C3B90A.55150BC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there a way to have punctual Read/Write access through BinFS : the = goal is to perform image updates in NAND Flash while executing in SDRAM --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_0015_01C3B90A.55150BC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there a way to have punctual = Read/Write access=20 through BinFS : the goal is to perform image updates in NAND Flash while = executing in SDRAM</FONT></DIV> <DIV><FONT face=3DArial size=3D2><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></FONT></DIV></BODY></HTML> ------=_NextPart_000_0015_01C3B90A.55150BC0-- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45600
  - 23
    - eshell equivalent under ce 4.2 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C3B90A.29E30060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there an equivalent app to eshell under PB 4.2 that would allow us to = perform image downloading through ethernet from a workstation that do = not have PB installed ? --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_000A_01C3B90A.29E30060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there an equivalent app to eshell = under PB 4.2=20 that would allow us to perform image downloading through ethernet from a = workstation that do not have PB installed ?</FONT></DIV> <DIV><FONT face=3DArial size=3D2><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></FONT></DIV></BODY></HTML> ------=_NextPart_000_000A_01C3B90A.29E30060-- Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45599
  - 24
    - Using an ISAPI extension I have written an ISAPI extension dll and have included in my build. It gets placed in the "Release" directory of the target and I can't cut and paste it to any other directory (an error 18 results). How can I specify what directory to write this dll to instead of it being placed in the "Release" directory automatically? Thanks, Jim Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45595
  - 25
    - IOCTL_DISK_SCAN_VOLUME documentation Hi, I am looking for IOCTL_DISK_SCAN_VOLUME input structure documentation. MSDN says there aren't any parameters passed to DeviceIOControl but I know there are some, specifically the #define SCANVOL_QUICK 0x00000001 parameter. Do you know of any other parameters that can be passed to the device driver with this I/O? Thanks, Anton Tag: FMD driver for 2048-bytes paged NAND flash Tag: 45593

Dear All,

I composed a FMD driver under PB 4.2. After the filesys.exe loaded it,
FMD_GetBlockStatus() is called for every block, then filesys.exe
corrupts. The call stack shows there is exception in file compactor.c,
fal.c and I can not find it under the folder \private.

Any advice is appreciated.

Top

Re: FMD driver for 2048-bytes paged NAND flash by Zhao

Zhao
Thu Dec 04 07:44:46 CST 2003

I've googled discuss groups. I know I must

1) disable FATFS caching
2) load 2 different FATFS DLLs in my image, for I have multiple volumes
with different sector size.

Zhao Kai wrote:

> Dear All,
>
> I composed a FMD driver under PB 4.2. After the filesys.exe loaded it,
> FMD_GetBlockStatus() is called for every block, then filesys.exe
> corrupts. The call stack shows there is exception in file compactor.c,
> fal.c and I can not find it under the folder \private.
>
> Any advice is appreciated.
>

Top

Re: FMD driver for 2048-bytes paged NAND flash by Zhao

Zhao
Sun Dec 07 19:48:32 CST 2003

Hi, everyone,

The problem is not solved even after I do so. The following is my
registry setting:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles]
"AutoMount"=dword:1
"AutoPart"=dword:0
"AutoFormat"=dword:0
"MountFlags"=dword:0
"DefaultFileSystem"="FATFS"
"PartitionDriver"="mspart.dll"
"Folder"="Mounted Volume"

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FriendlyName"="FAT FileSystem"
"Dll"="fatfsd.dll"
"Flags"=dword:00000024
"Paging"=dword:1
"CacheSize"=dword:ffffffff

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS2]
"FriendlyName"="FAT FileSystem"
"Dll"="fatfsd2.dll"
"Flags"=dword:00000024
"Paging"=dword:1
"CacheSize"=dword:ffffffff

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv]
"DefaultFileSystem"="BINFS"
"PartitionDriver"="mspart.dll"
"AutoMount"=dword:1
"AutoPart"=dword:1
"MountFlags"=dword:11
"Folder"="ResidentFlash"
"Name"="Microsoft Flash Disk"
"BootPhase"=dword:0

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv\FATFS2]
"MountFlags"=dword:2 ; support hive-based registry
"AutoMount"=dword:1
"AutoPart"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"MountFlags"=dword:0
"EnableCache"=dword:0

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS2]
"MountFlags"=dword:0
"EnableCache"=dword:0

When filysys.exe corrupts, the call stack list as following:

Call Stack: filesys.exe: 0x2FFE723E 17:26:38 12/04/2003 GTB Standard Time
FLASHDRV!CP_InitCompactor(_FlashInfo * 0x00000000) line 165
FLASHDRV!StartupFAL(_FlashInfo * 0x00000000) line 1461 + 8 bytes
FLASHDRV!DSK_Init(unsigned long 0x00000000) line 241 + 8 bytes
FSDMGR!CBlockDevice::OpenBlockDevice(CBlockDevice * const
0x00000000) line 117 + 16 bytes
FSDMGR!CStore::OpenDisk(CStore * const 0x00000000) line 230 + 4 bytes
FSDMGR!CStore::MountStore(CStore * const 0x00000000, int 0x0ffc9f12)
line 388 + 4 bytes
FSDMGR!AutoLoadFileSystems(unsigned long 0x00000000, unsigned long
0x0ffc9f12) line 553 + 12 bytes
FSDMGR!InitStorageManager(unsigned long 0x00000000) line 751
FSDMGR!Init(unsigned long 0x00000000) line 38 + 4 bytes
FILESYS!InitStorageManager(unsigned long 0x00000000) line 2248
FILESYS!prgInitRegistry(int 0x00000000, unsigned short * 0x0ffc9f12)
line 733
FILESYS!DoGeneralInit(unsigned short * 0x00046d74) line 2451 + 12 bytes
FILESYS!WinMain(HINSTANCE__ * 0x00000000, HINSTANCE__ * 0x00000000,
unsigned short * 0x8c258918, int 0x00000000) line 2849 + 12 bytes
COREDLL!MainThreadBaseFunc(void * 0x00000000, unsigned long
0x0ffc9f12, unsigned long 0x00000000, unsigned long 0x00000010, unsigned
long 0x00000005) line 405
End Call Stack: filesys.exe: 0x2FFE723E 17:26:38 12/04/2003 GTB
Standard Time

Have I missed something? Can anybody tell me why filesys.exe corrupts?

TIA

Zhao Kai wrote:
> I've googled discuss groups. I know I must
>
> 1) disable FATFS caching
> 2) load 2 different FATFS DLLs in my image, for I have multiple volumes
> with different sector size.
>
> Zhao Kai wrote:
>
>> Dear All,
>>
>> I composed a FMD driver under PB 4.2. After the filesys.exe loaded it,
>> FMD_GetBlockStatus() is called for every block, then filesys.exe
>> corrupts. The call stack shows there is exception in file compactor.c,
>> fal.c and I can not find it under the folder \private.
>>
>> Any advice is appreciated.
>>
>

Top