1. An endoscopic portal protective shield assembly comprising:
an elongate portal shaft with a viewing portal, the shaft having a slotted tubular body with an open interior surface, a distal end and a proximal end and a slotted opening in the distal end extending toward the proximal end partially along the slotted tubular body;
an elongated protective shield having a longitudinal shield body, a proximal end, a distal end; and
wherein the protective shield is configured to be slid into the slotted opening of the tubular body with an interior portion of the longitudinal shield body being inside the tubular body while maintaining the viewing portal open.
2. The endoscopic portal protective shield assembly of claim 1 wherein the protective shield body has a cross sectional shape or segment configured to fit against the interior surfaces of the shaft adjacent the slotted opening.
3. The endoscopic portal protective shield assembly of claim 1 wherein the proximal end of the protective shield has a shield handle.
4. The endoscopic portal protective shield assembly of claim 3 wherein the shield handle has an opening to align with a shaft body tab opening, and the shaft body has a tab at an end of the slot, the tab has the tab opening when the openings are aligned a fastener can fix the protective shield to the portal shaft.
5. The endoscopic portal protective shield assembly of claim 4 wherein the shield handle opening is threaded.
6. The endoscopic portal protective shield assembly of claim 5 wherein the shield handle includes a table arm adapter connector configured to be fixed to a table arm or otherwise clamped directly to a table arm.
7. The endoscopic portal protective shield assembly of claim 1 wherein the longitudinal shield body has a rib connecting the interior portion of the shield body interior of the portal shaft to an exterior portion of the shield body.
8. The endoscopic portal protective shield assembly of claim 7 wherein the exterior portion and the interior portion are spaced by the rib to receive and hold the slotted tubular body of the portal shaft adjacent the slotted opening.
9. The endoscopic portal protective shield assembly of claim 1 wherein the distal end of the protective shield extends past the distal end of the portal shaft on assembly.
10. The endoscopic portal protective shield assembly of claim 4 wherein upon insertion the assembly can be positioned and the portal shaft detached and withdrawn leaving the protective shield in place.
11. A method of treating a spinal injury or defect using an endoscopic portal protective shield assembly comprising the steps of:
making a small incision anteriorly or posteriorly for receiving an endoscopic portal protective shield assembly;
inserting the shield assembly;
viewing the nerve root, blood vessel or tissue to be shielded;
rotating a distal end of the shield to align with the nerve root, blood vessel or tissue;
detaching the protective shield from a tubular body of the endoscopic portal;
removing the tubular body leaving the protective shield in aligned position with and shielding the nerve root, blood vessel or tissue; and
completing the surgical repair removing the protective shield and closing the incision.
12. The method of claim 11 further comprises the step of passing a spinal implant device along the protective shield as a guide to insertion between two adjacent vertebrae.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method of accessing one or more file systems, the method including:
a scanning engine sending a request to a direct file system access engine, wherein the request bypasses an operating system kernel;
the direct file system access engine receiving the request and in response thereto sending a further request to at least one file system;
the direct file system access calling at least one operating system function to execute the request, wherein the at least one operating system function is not directly related to standard operating system functions used to execute the request;
the direct file system access engine receiving response information from the at least one file system; and
the direct file system access engine sending the response information to the scanning engine.
2. The method as claimed in claim 1, wherein the scanning engine is one or more of: a program, a driver, and an application.
3. The method as claimed in claim 1, wherein the direct file system access engine is one or more of: a program, a driver, and an application.
4. The method as claimed in claim 1, wherein the direct file system access engine is a kernel driver.
5. The method as claimed in claim 1, further comprising employing a kernel driver to use operating system functions that are not directly related to normal operating system functions used for the request.
6. The method as claimed in claim 1, wherein the request is related to one or more of: Enumerate Directory; Open File; Close File; Read File; Write File; Delete File; Query File Information; and Set File Information.
7. The method as claimed in claim 1, wherein the further request is at least partially obtained by compromising a user mode operating system.
8. The method as claimed in claim 1, wherein the further request is at least partially obtained by hooking one or more operating system programs.
9. The method as claimed in claim 1, wherein the further request is at least partially obtained by compromising a kernel mode operating system.
10. The method as claimed in claim 1, wherein the further request is at least partially obtained using a kernel mode Interrupt Descriptor Table (IDT) hook.
11. The method as claimed in claim 1, wherein the further request is at least partially obtained using a kernel mode SYSENTERSYSEXIT hook.
12. The method as claimed in claim 1, wherein the further request is at least partially obtained using a kernel mode Service Descriptor Table (SDT) hook.
13. The method as claimed in claim 1, wherein the further request is at least partially obtained using a kernel mode System Service Table (SST) hook.
14. The method as claimed in claim 1, wherein the further request is at least partially obtained using a kernel mode file system filter program.
15. A system for accessing one or more file systems, the system including:
a storage device to house at least part of a file system;
at least one memory to store a scanning engine and a direct file system access engine;
at least one processor, in communication with the at least one memory and the storage device, the at least one processor adapted to:
send a request from the scanning engine to the direct file system access engine, wherein the request bypasses an operating system kernel of the system;
allow the direct file system access engine to receive the request and in response thereto to send a further request to the file system;
allow the direct file system access to call at least one operating system function to execute the request, wherein the at least one operating system function is not directly related to standard operating system functions used to execute the request;
allow the direct file system access engine to receive response information from the file system; and
send the response information from the direct file system access engine to the scanning engine.
16. A computer program product for accessing one or more file systems, the computer program product comprising a non-transitory computer-readable storage device having instructions thereon, the instructions comprising:
(1) code programmed to send a request to a direct file system access engine, wherein the request bypasses an operating system kernel, the direct file system access engine receiving the request and in response thereto sending a further request to at least one file system, the direct file system access engine calling at least one operating system function to execute the request, wherein the at least one operating system function is not directly related to standard operating system functions used to execute the request, the direct file system access engine receiving response information from the at least one file system; and
(2) code programmed to receive the response information from the direct file system access engine.
17. The computer program product as claimed in claim 16, wherein the computer program product executes on a rooted computer.