The brand-new PN400 Phase Noise Test System is available for purchase! →

Spike fails to launch

Forums › General Discussions › Spike fails to launch

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #239500
    Hugh Shane
    Participant
    OS Name	Microsoft Windows 10 Pro
    Version	10.0.18363 Build 18363
    System Manufacturer	Dell Inc.
    System Model	XPS 15 7590
    System Type	x64-based PC
    Processor	Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s), 12 Logical Processor(s)

    Using SA44B Spectrum Analyzer

    This setup had been working fine for months. Now, for no apparent reason, when I start Spike, I see the little progress bar as it connects to the SA44B, and then nothing. I still see the Spike icon on the Windows task bar and Task Manager reports that Spike is active. But I see no Spike application window.

    #239501
    AndrewAndrew
    Moderator

    Hugh,

    Did you change the monitor configuration recently? If you went from 2 monitors to 1 for instance, it might put the application where the second screen used to be (off screen)

    Let’s try this. Close Spike and delete the file at this location.

    C:\Users\YourUserName\AppData\Roaming\SignalHound\Layout.ini

    Once deleted, restart Spike.

    If you don’t see the AppData folder at first, it is a hidden folder, you will have to “Show hidden folders” in the file explorer settings menu.

    Let me know if this resolves the problem.

    Andrew

    #248690
    andrewclegg
    Participant

    Andrew —

    I know this is an old thread, but I recently started having this problem. I deleted and reinstalled Spike, that didn’t work. I deleted the Layout.ini file as you suggest here, that didn’t work either. I’m running the latest Spike on Windows 11.

    I’ve run Spike with BB60Cs for 10+ years on a variety of computers, and haven’t encountered this before. And it was working fine on this computer two weeks ago, and now it doesn’t run. No changes to the config that I’m aware of in the meantime, other than updating to the latest Spike as part of troubleshooting.

    Any thoughts on how to proceed?

    Thanks.

    Andy

    #248693
    andrewclegg
    Participant

    Well, taking a hint from your proposed solution, I deleted (actually, just renamed) PowerOnPreset.ini too, and that fixed the problem. Sorry for the trouble.

    Andy

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.