New X1000

[Raziel]

...if i change the line back to use the redirections i end up with all sorts of error messages from programs which need the net which IS NOT available when the Workbench comes up, so i believe the line works for some the other way round?

No, it doesn't. AmigaDOS is quite logical in its ways . Run does what it does, never the opposite.

What you are seeing seems to be because the programs requiring network are not started from Network-Startup as they should, but either from User-Startup or WBStartup, so they will "overtake" your Network-Startup's efforts to start the network. Fix that, and the change I prescribed should work as intended.

Best regards,

Niels

Still not working as intended.

I use Wet and AmiUpdate and have put them network-startup (deleted them in WBStartup) and changed the startup-sequence to the right network-startup line.

But both programs will still come up with error messages about not finding a network...right now playing with DELAY (Wet) and TIMEOUT (AmiUpdate) to delay the first polling...

[kicko]

Thanks nbache. Changed the lines in startup-sequence and network-startup

[nbache]

Still not working as intended.

I use Wet and AmiUpdate and have put them network-startup (deleted them in WBStartup) and changed the startup-sequence to the right network-startup line.

But both programs will still come up with error messages about not finding a network...right now playing with DELAY (Wet) and TIMEOUT (AmiUpdate) to delay the first polling...

Strange.

Just to make sure: You did remember to remove the Run etc. from the AddNetInterface line in Network-Startup, right?

Apart from that, when I used an RTL8169-based card in my X1000, the network would often not come up even though AddNetInterface had returned. In the end, my solution was to put a Wait 5 SECS right after the AddNetInterface line. (Now I use an RTL8139-based card which doesn't have that problem, so I have commented out the wait again.)

I also have the following check after that:

Code: Select all

GetNetStatus CHECK INTERFACES,RESOLVER,DEFAULTROUTE
If WARN
  Wait 3 ; Increase chances of IPrefs having opened the final WB screen
  RequestChoice "Network Startup" "Network not operational,*nS:Network-Startup aborted" "OK"
  Quit
EndIf

Might give some clues, if nothing else. Although GetNetStatus can not necessarily detect all possible problems.

Best regards,

Niels

[Raziel]

Still not working as intended.

I use Wet and AmiUpdate and have put them network-startup (deleted them in WBStartup) and changed the startup-sequence to the right network-startup line.

But both programs will still come up with error messages about not finding a network...right now playing with DELAY (Wet) and TIMEOUT (AmiUpdate) to delay the first polling...

Strange.

Just to make sure: You did remember to remove the Run etc. from the AddNetInterface line in Network-Startup, right?

Apart from that, when I used an RTL8169-based card in my X1000, the network would often not come up even though AddNetInterface had returned. In the end, my solution was to put a Wait 5 SECS right after the AddNetInterface line. (Now I use an RTL8139-based card which doesn't have that problem, so I have commented out the wait again.)

I also have the following check after that:

Code: Select all

GetNetStatus CHECK INTERFACES,RESOLVER,DEFAULTROUTE
If WARN
  Wait 3 ; Increase chances of IPrefs having opened the final WB screen
  RequestChoice "Network Startup" "Network not operational,*nS:Network-Startup aborted" "OK"
  Quit
EndIf

Might give some clues, if nothing else. Although GetNetStatus can not necessarily detect all possible problems.

Best regards,

Niels

Yes, of course, no run in front of addnetinterfaces

hmm, your script gave me an idea, maybe i'm putting in an endless loop which waits for the network to be up before progressing...

...wait, wasn't the network-startup meant to do that in the first place?


EDIT:
Wet needs a DELAY of 20 here to work without an error window when WB has come up
AmiUpdate is still refusing to find a network (at the moment using also 20 for TIMEOUT (next check with 30)
...i just realized that TIMEOUT is meant to fix bad connections but has nothing to do with initial scanning delay...ah well

Edit2: For whoever stumbles over this in search of help (probably me in 30 years)
The reason for it not to work properly was that i missed to save WBStartup prefs after removing AmiUpdate from WBStartup list, so there were two times that AU was started giving this strange results. All goody now

[xenic]

Thanks everybody for all the information.

I have a couple of questions. Does the Compact Flash connector on the motherboard work?? If so, does it appear in HDToolBox if there is a Compact Flash installed?

I notice that there is a huge amount of graphics related debug output (dumpdebugbuffer output). Is that intentional or did someone forget to disable the debug output for users?

[nbache]

Does the Compact Flash connector on the motherboard work?? If so, does it appear in HDToolBox if there is a Compact Flash installed?

Yes, it works, but can only be used in CFE and Linux. There is currently no AmigaOS driver. And consequently, no, it can't be seen in HDToolbox (or rather Media Toolbox, as it's called in OS4).

I use mine to hold the Linux kernel I boot Debian from.

Best regards,

Niels

[amigakit]

Every Amiga has traditionally had the Amiga keys next to the Space bar- it doesnt matter what locale you are in. The X1000 is no exception to this.

If you are used to the PC computing world, then that is probably why you think the ALT should be adjacent to the Space bar.

Remeber you are buying a US Boing Ball Keyboard - not a standard PC keyboard. We did not misrepresent this fact on our website.

[xenic]

Every Amiga has traditionally had the Amiga keys next to the Space bar- it doesnt matter what locale you are in. The X1000 is no exception to this.

If you are used to the PC computing world, then that is probably why you think the ALT should be adjacent to the Space bar.

Remeber you are buying a US Boing Ball Keyboard - not a standard PC keyboard. We did not misrepresent this fact on our website.

My µA1 came with a PC keyboard and I continued to use the same keyboard with my SAM Flex. I've never owned a Windows PC but I am now accustomed to the PC keyboard layout. Since I've been advised in this topic that I can reverse the keys with an environmental variable and informed by AmigaKit that I can pop the keycaps and reverse them, there is no problem. However, the included sound card makes scratching noises at the beginning of almost every sound played and probably needs an updated driver. I've replaced the sound card with one that works well so that's not a problem for me now. I'm happy with my purchase and I'm happy with AmigaKit's service.

[xenic]

Does the Compact Flash connector on the motherboard work?? If so, does it appear in HDToolBox if there is a Compact Flash installed?

Yes, it works, but can only be used in CFE and Linux. There is currently no AmigaOS driver. And consequently, no, it can't be seen in HDToolbox (or rather Media Toolbox, as it's called in OS4).

I use mine to hold the Linux kernel I boot Debian from.

O.K. That will be nice with an AmigaOS driver. It seems like we are waiting on a number of drivers. I have one other question. I noticed that the new Kicklayout has 2 sets of modules. Do you (or anyone) know to specify with set of modules gets used? The Kicklayout text refers me to SYS:Documentation/kernel/bootloader.txt which doesn't exist.

[Severin]

You choose which one you want with the amigaboot.of screen where the kickstart is actually loaded, just stop the countdown and set your default option (I think, never set a different default) or just choose which one to boot from as needed.