CVI DLL target project needs to let caller update progress

I'm still thinking about this old topic of mine. 
If I ever get around to packaging my low-level project into a DLL, other host projects that use it won't necessarily be CVI.  So my DLL can't have upward CVI dependencies to let the caller know status of DLL function looping.
I've looked briefly into multithreading with pointers, but it seems to me that this would be machine/processor dependent.  I can't really use PostDeferredCall because of the CVI dependencies back up in the caller.
Should I simply increment an index in my loop and output that from the function by reference?  Something like this:
int DLLSTDCALL myFunction (int* progress)
double stuff;
// worker loop
for (int i=0; i<1000; i++)
stuff = rand();
*progress = i;
return;
And then just leave it up to the framework caller to handle the progress pointer in a multi-threaded fashion?

meh, it'll all work out.
I did some testing with multi-threading and it works pretty well to get visibility of real-time status.
I decided to leave it up to the client platform to deal with threads on their own if they want this visibility of a DLL function.

Similar Messages

  • Help needed with so-called "updates"

    I just now downloaded the "latest" adobe flash update, as prompted by Adobe.  Now I discover that the version downloaded on my computer is NOT the latest update.  This takes 45 min to do - what's up with this?  Why did it not give me the latest update?????  I have work to do on the computer and just cannot continue to take 45 min off to update something that isn't an update.

    This particular forum (sharing and storage) was created to help those transitioning from Photoshop.com to Adobe Revel. I am moving your post to the proper forum so that it can get proper attention.
    We also have many other forums relating to other Adobe products at: http://forums.adobe.com.

  • Is it possible to step into a CVI dll when called by TestStand?

    As the question says: "Is it possible to step into a CVI dll when called by TestStand?"
    I am sure Ray F. may have a few tricks up his sleeves...  Hope you see this post, Ray!
    I compiled a dll using CVI.  The dll is called as a test by TestStand.
    I do have an "exe" version of the code that I use for debug with a testbed, but the behaviour is not the same as testing the actual target while running TestStand.  My goal is to get as close as possible to the real events.
    Thanks,
    JLV

    Sorry about that,
    There are two ways as I was saying:
    1. You can configure the CVI adapter to Execute Steps in a External Instance of CVI (requires CVI 6.0 or greater).
    Only go to Configure->Adapters and select the LabWindows CVI adapter and click on configure and select the corresponding option.
    After that set a break point in the step that you want to debug.
    An external instance of CVI will be launched where you can set break points and step into the code.
    2. From CVI Specifying an external process:
    In CVI go to Run Specify External Process and enter the seqEdit.exe as the program name (you have to browse to the location <TestStand>\Bin\SeqEdit.exe).
    As the argument you enter the name of the sequence file you want to debug.
    Now just select Run->Debug SeqEdit.Exe
    The Sequence Edtior will be launched and you can set break point in your CVI code and step into it when the step is executed.
    Check the Using LabWindows/CVI with TestStand reference manual for more information.
    I hope it helps you to get started.
    Regards.

  • When using the new controls of CVI 7 in my DLL it crash on the DisplayPanel call

    I have a CVI DLL that was build under CVI 6. When I recompile it in CVI 7 everything works fine when I load the DLL from my application. But If I add a button on my uir file with the new CVI 7 style (no event code associated, just a plain button) my DLL crash and hang my main application on the DisplayPanel call. If I don't use the new controls (use the classic-style controls) everything works fine. I use LoadPanelEx to load my uir file. The returned panel handle is good (> 0) But when I call DisplayPanel it doesn't show me any error but just crash my DLL and jump back in the DLLMain function saying that my process is detaching and hang my main application.
    I am running on Win2k. I have
    LabVIEW 7 and LabVIEW 6.0.2 installed also. The main application that calls the DLL is made in Delphi 6.
    I have re-installed the run-time engine from the CDs but this didn't do the trick. Is there something else that I must include with my DLL to use thoses new controls styles. The DLL is running from the same place where it was build.

    Hi,
    I have created another cvi DLL and it create the same behavior in my application (crash on DisplayPanel). But if I do a standalone CVI executable with thoses new buttons everything is fine. Also I have created another application(in Delphi) to load the cvi-dll and it works fine in that one. So I would tend to say that it is in my application but on the other hand everything works fine if I don't put thoses LabStyle controls...Weird I know...
    In shorts It is just crashing with a specific application but for any UI project that I create. If I don't put thoses buttons everything is ok...Any other advises would be helpful because I'm kind of out of ideas...
    Gilles Hache

  • Intermittent problem with TestStand calling CVI DLL calling MSCV DLL

    Sorry about cross post, but I am not sure which group is best to address
    this issue.
    Setup:
    Windows 2000 SP1
    TestStand 2.01f
    CVI 6.0
    MSVC++ 6.0 SP5
    Problem:
    I have a CVI Test Library DLL that contains test functions called by
    TestStand using the C/CVI adapter. The CVI Test Library DLL in turn makes
    several calls to another DLL written in MSVC++. I am experiencing an
    intermittent problem with one of the MSVC functions. The problem ~appears~
    to be stack related, but I am not sure. Among other things, this MSVC
    function accepts a const char * argument that is a TestStand lookup string.
    The function uses this string to access the TestStand API.
    What happens is this: Everything works fine. I then recompile the CVI DLL
    after making some mod, then run. The MSVC++ DLL asserts that the const char
    * arg passed by the CVI DLL is NULL. However, this is not the case if I
    single step through the CVI code. It has happened both with passing
    variables as the const char * argument and as hardcoded strings literals, so
    its not that I am actually passing NULL. The other argument to this
    function is the TestStand sequence context dispatch pointer (LPDISPATCH
    pobjSequenceContextDisp) and it always ~appears~ to be passed correctly.
    The problem is frustrating and hard to debug because I can not
    deterministically reproduce it. The problem ~never~ appears when I debug my
    MSVC++ DLL in Visual Studio. And it only occasionally appears otherwise.
    The problem, when it appears, always appears on the first run after
    recompiling the CVI DLL, though the problem does not happen after ~every~
    recompilation. I'd say it happens 1 in 6 times after a recompile.
    Recompiling the exact same code does not always make the problem disappear.
    If I change the CVI code (code that has nothing to do with the argument
    itself though) and recompile the problem almost always goes away. Selecting
    'Mark all for compilation' and rebuilding does not make the problem go away.
    Only tweaking the CVI code and recompiling does (usually).
    Whats more, the problem appears:
    * With the CVI DLL built as Debug or Release mode.
    * With the CVI default calling convention set to __stdcall or __cdecl.
    * With the C/CVI TestStand adapter set to run in-process or external
    instance of CVI.
    The problem appears to be some sort of stack or argument passing problem
    between CVI and MSVC, though thats just a guess based on the symptoms. I
    have quadruple checked the calling conventions of all declared functions.
    The CVI DLL functions all use TX_TEST (which resolves to __cdecl). The MSVC
    DLL functions all explicitly use __stdcall. Is there a problem with calling
    __stdcall MSVC functions from a __cdecl CVI function?
    I can find no other memory leaks or indications of memory corruption
    elsewhere in either the CVI or MSVC DLLs. Its only this one function that
    exhibits this strange 'null const char *' problem.
    Can anyone offer any ideas about what may be causing this problem? Anything
    else I should check/verify?
    Regards,
    Joe

    Silvius,
    > Although I'm not sure if any of the following are the real cause of
    > your problem, I have the following suggestions:
    Thanks for the reply. At this point any and all suggestions are welcome...
    > 1. There could be a problem with calling
    > __stdcall MSVC functions from a __cdecl CVI function. As a workaround
    > wrap the _cdecl call inside a _stdcall call that is exposed or
    > exported to TestStand or vice-versa. This can be a problem because if
    > _cdecl is used, the calling function is responsible for cleaning up
    > the stack and if _stdcall is used, the called function is responsible
    > for cleaning up the stack.
    I was under the impression that as long as everything was explicitly and
    consistently declared, you could safely mix cdecl and stdcall f
    unction
    calls. Is it bad to do this? Is this a known issue with the CVI compiler?
    I've never seen a problem with doing this under MSVC++.
    I'll try wrapping them in cdecl calls for CVI - though we have a
    depressingly large number of stdcall functions in the MSVC DLL ;-). They
    need to remain stdcall in the DLL because we also call them from Visual
    Basic.
    > 2.Don't mix Debug version of one DLL with the Release version of the
    > other DLL. I had some bad experiences doing this and both DLLs where
    > developed in MSVC. Allways use either Debug either Release versions of
    > DLLs.
    I verified that the MSVC DLLs were either ALL Debug or Release. I too have
    seen nasty problems when MSVC Debug and Release is mixed.
    One thing I had not thought of until your reply: What about mixing CVI Debug
    DLLs with MSVC Release DLLs? Have you ever seen issues with doing this?
    Thanks!
    Joe

  • Calling test sequence from CVI DLL that use ATL COM object does not work

    I am trying to call some DLL function writen in CVI from teststand. The CVI DLL is using ATL COM object(Written by me).
    The ATL COM object making instance of several ATL COM object inside it (including two controls that contains dialog). If I use a client writen in VC++ 6 and use the ATL COM (writen by me) works perfectly. But if I try to use it from CVI DLL it does not work any more.
    What is wrong? The client is passing an IUnknow interface to my component. Can anybody explain me what is wrong?

    It is not clear from your question as to what is specifically failing. If possible, one option would be to remove TestStand from the picture and see if the problem still occurs using a CVI EXE that invokes the CVI DLL.
    Scott Richardson - NI
    Scott Richardson
    National Instruments

  • How to Load a Panel during run time from a CVI dll

    Hi,
    I want to execute/load a panel during runtime, from a CVI dll function.
    my CVI dll "test.dll" has "READ_PAN" function. while executing this function from a Test Stand Action step i want Configure Panel (from FR_GUI.uir) to pop up.
    can you please suggest me how can i do this from my "test" project of CVI.
    int __stdcall __export RunFRConfig (CAObjHandle step,CAObjHandle thisContext)
        ERRORINFO errorInfo;
        char errMsg[1024];
        int pan;
        pan = LoadPanelEx (0, "FR_GUI.uir", READ_PAN, __CVIUserHInst);
        DisplayPanel (pan);
        RunUserInterface();
        DiscardPanel (pan);
        return 0;
            Error:
       // sprintf(FinalErrMsg,"Configure Error: %s",errMsg);  
        return -1;

    Thanks for ur reply.
    Hello Asad,
    It is possible to maximize the run time previewer when calling reports from forms. U need to set a parameter named 'MAXIMIZE' to do that.
    I m attaching a code sample for u. This is working in my production environment.
    DECLARE
    pl_id ParamList;
    BEGIN
         pl_id := Get_Parameter_List('setProposal');
         IF NOT Id_Null(pl_id) THEN
              Destroy_Parameter_List( pl_id );
         END IF;
         pl_id := Create_Parameter_List('setProposal');
    // This parameter is set to hide parameter form at run time     
         Add_Parameter(pl_id, 'PARAMFORM', TEXT_PARAMETER, 'NO');
    // This parameter is used to maximize previewer window at run // time
         Add_Parameter(pl_id, 'MAXIMIZE', TEXT_PARAMETER, 'YES');
    Run_Product(REPORTS, 'sample.rep', SYNCHRONOUS, RUNTIME,
    FILESYSTEM, pl_id, NULL);
    END;
    Feel free to contact me if u need anymore assistance.
    Take care and bye

  • CVI dll crashes when it uses RefNum var passed in from other CVI code or from LV 2009. Why?

    Hi, all--I am pretty much a LabVIEW beginner, but starting to dry a little behind the ears.  Currently working on a project where the original LV code called VC CINs.  We want to convert the CINs (lvsbutil.exe--ick) to Call Library Function nodes and so I am working to convert the CIN code to a DLL.  Finally got everything compiled happily and went to run my VI calling the DLL--as far as I could tell, at the DLL call, CRASH!  So then, I fiddle around making a CVI main that I can use to call my crashing DLL(debug mode) from and I find the crash happens when I call FRefNumToFD, even though the RefNum seems to be legit.  I even tried inserting FIsARefNum in front of the conversion routine, and FIsARefNum crashes now too.  Is there a problem with these file manager functions?  Is there something freaky with RefNum passing between CVI and LV?
    I am using CVI 9.0 and LV 2009.  Thanks for all input!

    OK:  here is a screen shot of my vi, and some of the code from my CVI dll--
    //#include "extcode.h"
    #include "ShareLib_ProcessEF.h"  //The commented out stuff is in this header file
    /*typedef struct
     int32_t dimSize;
     uint16_t elt[1];
    } TD1;
    typedef TD1 **TD1Hdl;  */
    #define CHECKSUM ChecksumNew
    extern void CHECKSUM (uInt8 *pData, int32 Size, uInt16 *pXOR, uInt16 *pChk_sum);
    uInt8                 **hRead_buf;
    int32 __declspec(dllexport)ProcessEFBlock(LVRefNum *hFile, uint16_t *pChksum, uint16_t *pXOR, TD1Hdl hData_block,
     TD1Hdl hHdr_block, LVBoolean *pEOF, LVBoolean *pDLOK, LVBoolean *pSEND);
    int32 __declspec(dllexport)ProcessEFBlock(LVRefNum *hFile, uint16_t *pChksum, uint16_t *pXOR, TD1Hdl hData_block,
     TD1Hdl hHdr_block, LVBoolean *pEOF, LVBoolean *pDLOK, LVBoolean *pSEND)
      MgErr                 mgError;
      File                  fd;
      int32                 byte_count;
      uInt8                 size_buffer[2];
      int32                 read_buf_size;
      int32                 offset;
      uInt8                 *pRead_buf;
      uInt16                *pData_buf;
      uInt16                tmpChksum;
      int32                 i;
      uInt16                fill_count;
      int32                 DataBlockSize;
      uInt8                 **hTemp_buf;
      uInt8                 *pTemp_buf;
      uInt8                 fill_byte;
      BYTEWORD              byteword;
      BYTELONG              bytelong;
      Bool32    iRefNumErr;
      mgError = 0;
      // Convert file reference to file descriptor
      iRefNumErr = FIsARefNum(*hFile);  //This is where the code leaves to think things over
      if (mgError = (FRefNumToFD (*hFile, &fd)))
        goto out;
      } // if   
    Attachments:
    dll_call.jpg ‏45 KB

  • Make panel modal from a CVI dll

    I'm creating a CVI dll.  It will popup a main panel.  I need this panel to be a modal, just like a dialog window, user must exist before they can return to the caller.
    The InstallPopup function doesn't work in this case.
    By the way, I have additional popup panels on top of the main panel.  They are working ok with the InstallPopup function.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

    George:
    CVI doesn't create system modal windows.  InstallPopup creates application modal windows: the window (or panel) stays on top of other windows in the same application, but other applications can go active on top of the installed popups.
    You could make the panel floating, which will have it be always on top, but not necessarily the foreground or active window.  To make a panel float, you can do it programmatically using
    SetPanelAttribute (panelHandle, ATTR_FLOATING, VAL_FLOAT_ALWAYS);
    or you can do it in the UI editor by double-clicking on a blank spot in the panel, and then click on Other Attributes, and set the Floating Style.  Having the panel float will keep it on top so it won't get lost under other windows, but other applications can still be active.
    You could also use a timer to force your window to be the foreground window using the Win32 API (or Windows SDK) SetForegroundWindow() function.  This isn't a perfect solution, and you may see some strange behaviour on background windows if you really try to get them to be active, but it helps avoid an inadvertant click forcing the user to search for the desired window.
    The attached appliaction uses a timer and SetForegroundWindow() to keep the panels on top.  It also calls InstallPopup to install a popup on top of the main panel, and sets the popup to be the foreground window.  There are some additional details in comments in the code and in text boxes on the panels.
    The Win32 API (or Windows SDK, depending on which CVI version you have) isn't installed by default.  If it's not installed, you just need to reinstall CVI, selecting the Win32 API as an option.  Note that you need to use the version that ships with CVI, not VC++ or other development tool.
    Attachments:
    modalpanels.zip ‏6 KB

  • If I no longer have the old application Backup installed on my Mac (part of the .Mac subscription), do I still need the folder called Backup, that is in my Library in the Application Support folder?

    If I no longer have the old application Backup installed on my Mac (for performing scheduled backups of data on the computer), do I need the folder called Backup, that is in my Hard Drive, to Library, to the Application Support folder?  (There is no Backup folder in my Home Folder, to Library, to the Application Support folder.) 
    Backup was part of the .Mac subscription I used to have, and I have not used it since I gave up being a .Mac subscriber many years ago.  In fact I recall Apple saying at one point that they no longer supported the Backup Application.  I assume the Backup folder is just remnants from when I used to have that application, however I could be wrong, and don't want to trash the folder unwisely.
    As I looked through the various items in the Backup folder, nothing appears to be modified since 2007, which further confirms that this folder is from long ago when I used to have that application.  I did notice that the main Backup folder itself was the only thing that had a more current modification date on it.  That date coincides with the date that I installed Snow Leopard on my Mac earlier this year.  But I'm assuming that any operating system software installation will place a modification date on all the various folders of one's computer, with the date the new OS was installed.
    Any insight will be appreciated!  Thank you!

    Since it has always been very basic to backup your computer and all it's data, Apple provides no way for you to transfer music from your iPhone back to your computer.  As you know, you can re-download all iTunes purchases, but music that you ripped yourself you'll have to just re-rip again.
    You can try and find 3rd party applications that might help you.  I'm sure you'll pay, however.
    Let this be a very important lesson learned.
    Best.

  • Target system(Destination) for RFC call ?

    Need some help in calling an RFC for xi interface.
    For triggering the data in to xi , RFC needs to be called. This RFC can be called using an ABAP Program / report . BUT inorder to call that RFC a Destination / Target system needs to be defined . Even though RFC destinations can be managed by transaction SM59 what will be the target system for calling this RFC in a generic sense?
    Like what destination i should be expecting this code : ?
    REPORT  Z_TEST.
    CALL FUNCTION 'ZFunctest' destination ????
    Please suggest
    Krishna

    Yes i now understand the scenario : well is this statment correct ?
    When we say like this :
    CALL Function 'ZTEST' Destination SIDCLNT015
    does this mean ZTEST should be there in destination system ? which means the RFC i am writing should be there on xi systems whose system id is SID ?
    As i heard some where that ZTEST should be there on targetsystem i call for ?
    Please suggest
    Krishna

  • Creating a DLL in Labview 8.6 and calling it from Visual Basic 6.0

    Dear friends,
    I need to create a DLL in Labview 8.6 and call it from Visual Basic 6.0. The system works as follows:
    I made an application using Labview 8.6 + Vision Assistant 8.6 where I can obtain the x,y coordinates of a template in an certain image being captured by an USB camera. The template coordinates change every time it moves and Visual Basic 6.0 must read these x,y values in real time. I found some information in the link http://zone.ni.com/devzone/cda/tut/p/id/3925, but it works for version 6.x of Labview and 8.6 version is different. Am I in the right path? If you have an updated tutorial like the one in the link above but for Labview 8.6 It would be very nice. Please help me.
    Kind regards.
    João Júnior

    Hello Osvaldo,
    I analysed the updated tutorial you sent me, but the thing is that it doen't show how to create the DLL in LV 8.6 but only show how to accessing the DLL from VB6. My problem is really HOW TO CREATE THE DLL IN LV8.6. In the link http://zone.ni.com/devzone/cda/tut/p/id/3063 there is detailed information about how to do this in LV6.x, the problem is that I don't find the path Tools»Build Application or Shared Library (DLL) in LV8.6, I think the procedure in LV8.6 is a little bit different. Don´t you have an updated tutorial on how to build a dll in LV8.6?How could you help me?
    Kind regards.
    João Júnior

  • How do I change what third party DLLs my project is linking to in LabWindows 8?

    So my company has an extension written in c built with LabWindows 8 it is an extension for the Tcl scripting language. After I build the application the resulting DLL is dependant on another DLL: tcl84.dll. Also, these lines is generated in the .cws file:
    [DLLs Used By Executable 0001]
    DLL 0001 = "/C/Tcl/bin/tcl84.dll"
    This DLL is not needed by the project as we have several other extensions for Tcl also written in LabWindows that do not have this dependancy. To my surprise however, the other extensions we have for Tcl also have the above line in thier .cws file. Yet the are not listed as a dependency when I examine them with a program like Dependency Walker and the extensions run properly when I remove tcl84.dll from the system.
    I have tried deleting the line from the project file and LabWindows simply regenrates it upon my next build. Also, I made an entirely new project carrying over only the .c and .h files and setting up the new project from scratch, but LabWindows still auto-generates those lines when I get my first successful build.
    I've included the entire project directory in my post.
    Solved!
    Go to Solution.
    Attachments:
    SI Project.zip ‏87 KB

    Edna-S wrote:
    Does this tcl84.dll interfere with your dll?
    http://www.ni.com/white-paper/8911/en
    Yes, I need to be able to use this dll with tcl 8.6 but tcl84.dll restricts it to only be used on tcl 8.4.
    That link appears to be involved only with the tcl side of things rather than how LabWindows interacts with dlls.

  • CVI.dll crashes 2013 when trying to browse

    If I attempt to anything that requires a browse/file select LabWindows crashes with the following report:
    Problem signature:
    Problem Event Name: BEX
    Application Name: cvi.exe
    Application Version: 13.0.0.632
    Application Timestamp: 51cb679b
    Fault Module Name: CVI.dll
    Fault Module Version: 13.0.0.632
    Fault Module Timestamp: 51cb6792
    Exception Offset: 00a4bb50
    Exception Code: c0000409
    Exception Data&colon; 00000000
    OS Version: 6.1.7601.2.1.0.256.4
    Locale ID: 1033
    Additional Information 1: 7d8b
    Additional Information 2: 7d8b59960e847456f719cf8b76eb40a7
    Additional Information 3: 1aa0
    Additional Information 4: 1aa00fb74513a107a85e25616fae3f2c
    Cannot add existing files to project, open new project or open workspace.
    Started after loading NI-VISA.

    Hi jimbrown60,
    Do you see this problem after upgrading to LabWindows/CVI 2013 SP2? 
    Can you provide system information such as OS, OS-bitness, other software currently installed?
    Have you tried running LabWindows/CVI as an Administrator (i.e., right-clicking LabWindows/CVI and selecting Run as administrator)? Does this cause a change in behavior?
    Are there any errors logged in Windows Event Viewer? If so, could you clear the event log, reproduce the issue, and send the list of events logged?
    Thanks,
    Daniel D.
    National Instruments
    Automated Test Software R&D

  • LV 6.0.2: an App-built dll gives a runtime error when called by C

    I want to use Labview 6.0.2 VIs as DLL's in a Borland C++ Project.
    Starting with the simple I have made a VI that returns a constant int32 then built a dll with the Application Builder and put the dll and include file in a BC++ project directory. Compile and link seems to run well. But when excuting the call to the LV fuction gives Fatal Error: labview.lib was not called from a Labview process.
    It seems this question was posted before, but answer didn't help me, Sorry.
    7.1 -- 2013
    CLA

    Hi Gabriela -
    This question is answered in the KB article entitled : "LabVIEW.LIB Error When Calling a DLL Built with LabVIEW"
    The link for this document is -> http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/a4c3aef93240280a86256931006fb66c?OpenDocument
    Or you can go directly to www.ni.com/support and search for this document and others to help.
    The reason for this is that the old labview.lib does not know how to correctly locate the LabVIEW Run-Time Engine when called.
    From the document I posted ->
    Your dll is most likely making a call If you want to call a Windows DLL or CIN built with a version of cintools before LabVIEW 6.0, you must relink the DLL with the labview.lib from 6.0. If you call an old DLL or CIN in your LabVIE
    W DLL, you receive the aforementioned error and the application terminates, because the old labview.lib does not know how to correctly locate the LabVIEW Run-Time Engine when called in this situation.
    Good luck-
    ben schulte
    national instruments

Maybe you are looking for

  • Is it possible to Install Windows 8 Pro 64-bit on a secondary hard dive in Mac Mini (Late 2012) using Boot Camp 5?

    Hello, I have a Mac Mini (Late 2012) running on OS X 10.8.3 and would like to install Windows 8 Pro on a secondary hard drive using Boot Camp 5. Is that really possible? A little background about the topic under discussion. 1. Mac Mini (Late 2012) ha

  • Can anyone help with me on characterstics and Keyfigures in BPS Planning

    Hi,    How are you folks ?. I am seeking for help for characterstics and keyfigures for Inventory planning, production planning and for headcount planning. Can any one help me with the data.    I would appreciate if anyone let me know on it.         

  • Receiving Unsolicited Facetime Requests

    I keep receiving unsolicited Facetime requests on my iPhone.  I noticed in the morning that this person attempted to Facetime with me during the odd hours of the night, and in the morning they tried to connect again.  I wasn't sure if I actually knew

  • Cisco Catalyst 2980G

    Hi all, I am currently studying for my CCNA and have acquired some cisco equipment to help me with this. One of the devices I have is a Cat 2980G 80 port but for some reason I am unable to connect to it via the console port.  All my other switches an

  • How do I recover and unlock it

    ok so my ipod 4th generation won't go into recovery mode cause my home button won't register and my ipod is locked for 22 million minute