search

albertstarfield / project-zephyrine

Introducing Project Zephyrine: Elevating Your Interaction Plug and Play, and Employing GPU Acceleration within a Modernized Automata Local Graphical User Interface.
MIT License
19 stars 1 forks source link

[BUG] Native Windows #1

Open bunnywaffle opened 1 year ago

bunnywaffle commented 1 year ago

Describe the bug When installing it, when I try to run this command: ./run.ps1 , PowerShell shows me this error.

To Reproduce Steps to reproduce the behavior:

  1. run this ./run.ps1
  2. See error

Expected behavior A clear and concise description of what you expected to happen.

alpaca-electron should have run after running that command.

Screenshots If applicable, add screenshots to help explain your problem. image

Desktop (please complete the following information):

Additional context Add any other context about the problem here.

ReconIII commented 1 year ago

The error message you're receiving is indicating that the execution policy on your system is preventing you from running unsigned scripts.

You can change the execution policy to allow running unsigned scripts, but please be aware that this can have security implications, especially if you run scripts from untrusted sources.

To change the execution policy for the current session only, you can run: Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

But even when I do that it says "Unsupported platform: Windows_NT"...

bunnywaffle commented 1 year ago

Still giving me the same error.

image

ReconIII commented 1 year ago

Still giving me the same error.

image

This might be a case where it just can't find the ./run.ps1 file? :/ idk I am not involved. I can't get it to run either. I reached out to Albert for more clarity on where these files are supposed to be placed? Are they to be placed in the root of the alapaca-electron folder? Hopefully he will reply here, otherwise I will let you know if he gets back to me.

albertstarfield commented 1 year ago

Hello! Firstly, thank you for giving the .ps1 script or program a try on Windows. Unfortunately, it appears that the conversion from the shell script to PowerShell script using AI didn't go smoothly. As a result, I've made the decision to rework the script from scratch. This might take some time, but I want to ensure its functionality. While waiting, you might want to explore using WSL2 with the GUI feature, WSLg. I appreciate your patience, and I'll keep this issue open until the script can run seamlessly on both native Windows 10 and 11. Thank you!

albertstarfield commented 1 year ago

Hi there, I am delighted to share with you the current strides made towards resolving this issue. The advancements are delineated as follows:

  1. Our endeavors extend to bolster Windows support, albeit excluding arm64 Windows due to resource constraints for development.
  2. Subtle refinements have been woven into the central codebase (index.js) to foster greater compatibility with Windows NT, particularly pertaining to directory path resolution.
  3. The script responsible for initiating Windows execution has been reset, primed for tailored rewriting to align with Windows specifics.
  4. Streamlining the launch procedure has been a priority, ensuring that valuable time is not squandered on processes like excessive repackaging.
  5. Advancements have been made in procuring acceleration resources such as CUDA, OpenCL, OpenBLAS, and Windows-specific binaries. These resources are curated from the official Falcon (ggllm.cpp) and LLaMa GitHub Release pages. It is pertinent to note that Windows compatibility is currently confined to the Falcon and LLaMa ggml models exclusively.

While I extend an invitation for you to explore the repository, navigate to the 'usr' directory, and initiate 'npm start,' I must underscore that, owing to ongoing development, the functionality might not be assured at this juncture. Your patience and understanding are deeply appreciated.