[GH-ISSUE #2706] WIN10处理器intel用那个?[Feature Request] #2159

Closed
opened 2026-05-05 13:23:22 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @pc18189 on GitHub (Dec 18, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2706

Describe the feature request

WIN10处理器intel用那个FRP?我看到有两个

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @pc18189 on GitHub (Dec 18, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2706 ### Describe the feature request WIN10处理器intel用那个FRP?我看到有两个 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:23:22 -06:00
Author
Owner

@pc18189 commented on GitHub (Dec 18, 2021):

image

<!-- gh-comment-id:997155859 --> @pc18189 commented on GitHub (Dec 18, 2021): ![image](https://user-images.githubusercontent.com/94864701/146632132-d903c1cb-969f-465f-a3ba-fe1b7f240cf8.png)
Author
Owner

@jiayaoO3O commented on GitHub (Dec 23, 2021):

我要是开发看到这样提issue真的拳头都硬了.

<!-- gh-comment-id:1000073591 --> @jiayaoO3O commented on GitHub (Dec 23, 2021): 我要是开发看到这样提issue真的拳头都硬了.
Author
Owner

@pc18189 commented on GitHub (Dec 23, 2021):

很抱歉我是小白,请原谅

佳瑶 @.***> 于2021年12月23日周四 14:25写道:

我要是开发看到这样提issue真的拳头都硬了.


Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/2706#issuecomment-1000073591, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWTYKPMIYFTX2BVWDYJUTXDUSK6E5ANCNFSM5KKJABTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1000429222 --> @pc18189 commented on GitHub (Dec 23, 2021): 很抱歉我是小白,请原谅 佳瑶 ***@***.***> 于2021年12月23日周四 14:25写道: > 我要是开发看到这样提issue真的拳头都硬了. > > — > Reply to this email directly, view it on GitHub > <https://github.com/fatedier/frp/issues/2706#issuecomment-1000073591>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AWTYKPMIYFTX2BVWDYJUTXDUSK6E5ANCNFSM5KKJABTQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@jiayaoO3O commented on GitHub (Dec 24, 2021):

如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白, 看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了, 你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎.

<!-- gh-comment-id:1000616020 --> @jiayaoO3O commented on GitHub (Dec 24, 2021): 如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白, 看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了, 你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎.
Author
Owner

@pc18189 commented on GitHub (Dec 24, 2021):

谢谢,我之前还问了一个问题。你可以看看吗?
https://github.com/fatedier/frp/issues/2671

佳瑶 @.***> 于2021年12月24日周五 10:31写道:

如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白,
看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了,
你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎.


Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/2706#issuecomment-1000616020, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWTYKPL7VJEUM6NYGYLQICDUSPLRNANCNFSM5KKJABTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1000682753 --> @pc18189 commented on GitHub (Dec 24, 2021): 谢谢,我之前还问了一个问题。你可以看看吗? https://github.com/fatedier/frp/issues/2671 佳瑶 ***@***.***> 于2021年12月24日周五 10:31写道: > 如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白, > 看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了, > 你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎. > > — > Reply to this email directly, view it on GitHub > <https://github.com/fatedier/frp/issues/2706#issuecomment-1000616020>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AWTYKPL7VJEUM6NYGYLQICDUSPLRNANCNFSM5KKJABTQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@pc18189 commented on GitHub (Dec 24, 2021):

高手在吗?帮忙看看下面的东西,它没有视频教程我想学都没门。
我想用自已的服务器,但是不知怎么把服务端建上去。它有安卓客户端使用很方便我工作上的需要
https://meta.appinn.net/t/topic/9616
https://github.com/xapanyun/4gproxy

生王 @.***> 于2021年12月24日周五 14:40写道:

谢谢,我之前还问了一个问题。你可以看看吗?
https://github.com/fatedier/frp/issues/2671

佳瑶 @.***> 于2021年12月24日周五 10:31写道:

如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白,
看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了,
你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎.


Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/2706#issuecomment-1000616020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWTYKPL7VJEUM6NYGYLQICDUSPLRNANCNFSM5KKJABTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1000724768 --> @pc18189 commented on GitHub (Dec 24, 2021): 高手在吗?帮忙看看下面的东西,它没有视频教程我想学都没门。 我想用自已的服务器,但是不知怎么把服务端建上去。它有安卓客户端使用很方便我工作上的需要 https://meta.appinn.net/t/topic/9616 https://github.com/xapanyun/4gproxy 生王 ***@***.***> 于2021年12月24日周五 14:40写道: > 谢谢,我之前还问了一个问题。你可以看看吗? > https://github.com/fatedier/frp/issues/2671 > > 佳瑶 ***@***.***> 于2021年12月24日周五 10:31写道: > >> 如果你的cpu是32位的, 就选386, 如果你的cpu是64位的, 就选amd64, 如果你是小白, >> 看到这两个文件名称只有"386"和"amd64"的区别, 那你只需要上网搜"386和amd64是什么意思", 马上就能知道他们之间的区别了, >> 你这样开一个Feature Request, 人家大佬直接close你又显得不近人情, 不close你又毫无营养, 哎. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/fatedier/frp/issues/2706#issuecomment-1000616020>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AWTYKPL7VJEUM6NYGYLQICDUSPLRNANCNFSM5KKJABTQ> >> . >> Triage notifications on the go with GitHub Mobile for iOS >> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >> or Android >> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >> >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1019607946 --> @github-actions[bot] commented on GitHub (Jan 24, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2159
No description provided.