T
Tony
I have been working with various MinLogon images for my initial
development, but I have been told that I will need to create a Kernel
image for the final product to help protect against unexpected
shutdowns.
Q1) Is it true that Kernel images are better suited for unexpected
power losses, or is that a myth?
Also, our application requires support for TCP/IP communication (=
tools like netsh, etc), sockets, access to event logs, parallel port
access, and others. I have all this working well in a MinLogon image
that is ~60MB, which an acceptable size for my application. I tried
many times to add all this support starting from a kernel
configuration each time, but I always end up with a MinLogon
cinfiguration at best. I haven't added EWF yet, but I will need it
too.
Q2) Are any of the features I listed above incompatible with a Kernel
configuration? Is that why I keep ending up with a MinLogon
configuration?
Thanks.
- Tony
development, but I have been told that I will need to create a Kernel
image for the final product to help protect against unexpected
shutdowns.
Q1) Is it true that Kernel images are better suited for unexpected
power losses, or is that a myth?
Also, our application requires support for TCP/IP communication (=
tools like netsh, etc), sockets, access to event logs, parallel port
access, and others. I have all this working well in a MinLogon image
that is ~60MB, which an acceptable size for my application. I tried
many times to add all this support starting from a kernel
configuration each time, but I always end up with a MinLogon
cinfiguration at best. I haven't added EWF yet, but I will need it
too.
Q2) Are any of the features I listed above incompatible with a Kernel
configuration? Is that why I keep ending up with a MinLogon
configuration?
Thanks.
- Tony