RE: Boot from H.D. But I do not see any Hard Disk In Target Window

From: Robert Magyar (RobertMagyar_at_discussions.microsoft.com)
Date: 06/29/04 

Date: Tue, 29 Jun 2004 09:26:17 -0700

In PB, if you goto Platform\Resolve Feastures\Storage Devices is it resolved?

Also try booting a debug image, and checking to see if there are any error messages. 

-- 
Robert
"Vincent Hung" wrote:
> In my CE platform builder 
> I had add the neccesary drivers in work space as below
> 
> 1 "ATAPI PCI/IDE Storage Block Driver" in Storage Devices
> 2 "FAT File System" in the storage manager of File Systems 
> 3. The Third Party driver "VIA ATAPI PCI/IDE Storage Block Driver" 
> 
> In the target, there isn't any "hard disk" in storage manager.
> The Hard Disk was divieded into three drives.
> it was formated  as FAT16. 
> CE image was placed on C:
> 
> After booting from MS-DOS 6.2, "mkdisk" was really executed. 
> 
> Did any important driver or file miss ? 
>  
> 
> 
> 
> "Robert Magyar" wrote:
> > Did you include a 'Storage Device' and 'File System' in your platform? 
> > 
> > In the your feature view you should be able to see a 'Storage Device' and under your device File Systems and Data Store you should have a Storage Manger and File System.
> > 
> > If not, add them to your platform.
> > -- 
> > Robert
> > 
> > 
> > "VincentHung" wrote:
> > 
> > > The platform chipset is based on VIA CLE266+VT8235 and CPU is VIA EDEN 733.
> > > 
> > > I try to place NK.BIN in the Hard Disk, 
> > > then The target can boot up from the Hard Disk. 
> > > But I have a pboblem. 
> > > To double-click the icon "My Computer" to enter another file folder.
> > > There does not exist any Hard Disk storage Device.
> > > My Windows CE platform builderis built in CEPC,
> > > The third  party device drivers are already added in. 
> > > 
> > > Anyone can advise me?? 
> > > Thanks so much...
> > >

Relevant Pages

  • Re: About FAT16 file system cache
    ... This is a storage ... and file system question. ... driver only writes when the filesystem driver tells it to do so. ... I used WinDBG to debug and found FAT file system would write the ...
    (microsoft.public.win32.programmer.kernel)
  • RE: Boot from H.D. But I do not see any Hard Disk In Target Window
    ... "ATAPI PCI/IDE Storage Block Driver" in Storage Devices ... The Third Party driver "VIA ATAPI PCI/IDE Storage Block Driver" ... there isn't any "hard disk" in storage manager. ... > In the your feature view you should be able to see a 'Storage Device' and under your device File Systems and Data Store you should have a Storage Manger and File System. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Virtual fodler with drive letter
    ... I know how to write a kernel mode driver. ... perceive it as a "file system", ... There had been couple solution out there for Windows users to use other form ... of storage as a "virtual file system" - such the one that uses google email ...
    (microsoft.public.win32.programmer.kernel)
  • Re: EMC to IBM SAN LUN replication
    ... Rather, trying to 'put it inside the SAN on a storage appliance' has severe limitations, but you don't seem to understand them. ... If you posit a shared-storage file system to allow your applications transparent file-level access, then the observations above about applications apply equally to the file system's internal operation. ... Of course, what you've described isn't a very broadly-useful cache, but just a means of supporting lazy inter-site replication. ... "you need something in the replication layer that understands synchronization issues at the file system" ...
    (comp.arch.storage)
  • Re: EMC to IBM SAN LUN replication
    ... you've characterized as 'emerging technology' is in fact very old hat: VMS had it over two decades ago, IBM had it a decade ago in Parallel Sysplex, other Unixes have been developing it more recently, as well as third-parties: it's Windows that's the real laggard. ... you can use the inter-site VMS cluster as a distributed CIFS file server to serve Windows clients - in the manner that you suggested using a distributed 'storage appliance'. ... Only if a) that storage appliance is interlocking raw block access synchronously and b) you're using higher-level shared-storage distributed file system software for file-level accesses. ... Now, if you're using 'distributed cache' to mean something much more like 'distributed locking mechanism' (which tracks potential synchronization issues such that they can be properly addressed should they occur), then we're just using different terminology to describe the same thing. ...
    (comp.arch.storage)