Device not ready yet? Delaying x seconds.

Post bug reports related to either the kiosk ISO or the kiosk wizard here.
jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Device not ready yet? Delaying x seconds.

Post#1 by jmalon » 04 Jun 2013, 19:56

I'm using porteus-kiosk-wizard-v2.0.3-noarch (2013-May-27) to create a new PKE ISO file. I currently get the message, "Device not ready yet? Delaying x seconds. Error: Porteus data not found. Startup cannot continue." when booting with the new ISO. I've tried recreating and reburning the ISO with the same result.

With this new ISO, I'm trying to use the rootcopy directory instead of the unsquashing / modifying / squashing technique I'm used to using, so the issues may or may not be related to the Device not ready yet message.

Below is what I'm doing with the rootcopy folder before building the ISO:

/tmp/custom-kiosk/porteus/rootcopy/home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js (The original file plus my additional lines for using our proxy server. Should this just be my additions?)
/tmp/custom-kiosk/porteus/rootcopy/etc/rc.d/rc.Firewall (The original file plus an additional line of "iptables -A OUTPUT -p tcp --dport 3128 -m state --state NEW,ESTABLISHED -j ACCEPT".)
/tmp/custom-kiosk/porteus/rootcopy/etc/X11/xorg.conf.d/99-calibration.conf (Not in the original Porteus Kiosk Edition. This is my configuration file for touchscreen monitors. This has worked previously.)

Does this seem right? I'm building the ISO on Linux Mint 13 (Maya).

Any help would be appreciated. Thank you in advance.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Device not ready yet? Delaying x seconds.

Post#2 by fanthom » 04 Jun 2013, 20:11

hi jmalon,

are you booting from CD or usb? did it work with a previous version?
please boot once again and when you get a failure you'll be dropped to the shell so please run 'blkid' command and check if you get:

Code: Select all

LABEL="Porteus-Kiosk" TYPE="iso9660"
if not then please post output of 'lspci -knn' and 'lsusb -t' when in Mint so i can track the driver which is missing.

btw: moving this thread to 'Bug Reports'
Please add [Solved] to your thread title if the solution was found.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#3 by jmalon » 04 Jun 2013, 20:31

This may end up being a hard drive issue. I rebooted too so /tmp would be cleared out and I could get a fresh start and /tmp did not want to mount. Perhaps the files are getting corrupted?

Anyway, here are the results:

1. I'm booting from a CD in a Dell OptiPlex 755 (Intel Core 2 Duo).
2. Yes, this has worked previously using v2.0.3 but I was not using my rootcopy additions except for the touchscreen config and the Dell OptiPlex 755 is a recent addition.
3. After the error, when I run blkid I get: /dev/sr0: LABEL=Porteus-Kiosk" TYPE="iso9660"
4. On my Mint box:

Code: Select all

lspci -knn returns:
00:00.0 Host bridge [0600]: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub [8086:2580] (rev 04)
	Subsystem: Dell Device [1028:0179]
00:01.0 PCI bridge [0604]: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port [8086:2581] (rev 04)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d3)
00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: snd_intel8x0
	Kernel modules: snd-intel8x0
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge [8086:2640] (rev 03)
	Kernel modules: iTCO_wdt, intel-rng
00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03)
	Subsystem: Dell Device [1028:0179]
	Kernel driver in use: ata_piix
00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel modules: i2c-i801
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8321]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_current, nvidia_current_updates, nouveau, nvidiafb
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express [14e4:1677] (rev 01)
	Subsystem: Dell Optiplex GX280 [1028:0179]
	Kernel driver in use: tg3
	Kernel modules: tg3

lsusb -t returns:
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M
Should I run these commands on the box I'm trying to boot? The box I'm trying to boot the CD with is a Dell OptiPlex 755 (Intel Core 2 Duo). It has been running Linux Mint 15 fine as well as other bootable CDs.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Device not ready yet? Delaying x seconds.

Post#4 by fanthom » 04 Jun 2013, 21:11

3. After the error, when I run blkid I get: /dev/sr0: LABEL=Porteus-Kiosk" TYPE="iso9660"
ok - so this is not a kernel fault as your controller was initialized.
i suspect an issue with hardware (bad burn) or you mixed initrds between Kiosk versions.

kiosk 2.0.4 will be out within a second so please try it and if you get the same error then (after dropping to the shell) please mount /dev/sr0 manually and check if you can access porteus-kiosk-v2.0.4.sgn (this file is being searched for by initrd)
sample:

Code: Select all

mkdir /tmp/test
mount /dev/sr0 /tmp/test
ls /tmp/test/porteus
now:
- if you can see 'porteus-kiosk-v2.0.4.sgn' then everything is ok
- if you see .sgn file but with different version then your setup got mixed up (initrd is looking for a different sgn file than is in /porteus folder)
- if you get an error along the way then please report at which stage

thanks

btw: i was asking about the lspci/lsusb commands from the PC you are booting Kiosk but it doesn't matter now since we know that kernel is ok.
Please add [Solved] to your thread title if the solution was found.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#5 by jmalon » 04 Jun 2013, 21:27

I rebooted. Got the 2.0.4 wizard. Ran it and got an MD5 checksum mismatch error when running the wizard.

http://ponce.cc/porteus/i486/packages/kiosk/ show the newer files.

porteus-kiosk-v2.0.4-i486.iso 2013-Jun-03 15:40:08 38.5M application/iso-image
porteus-kiosk-wizard-v2.0.4-noarch.run 2013-Jun-03 15:25:55 539.0K application/octet-stream
porteus-kiosk.txt 2013-Jun-03 15:50:02 0.2K text/plain

I'll try again later. Maybe it just needs more time.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#6 by jmalon » 05 Jun 2013, 14:38

This morning I redownloaded and ran the porteus-kiosk-wizard-v2.0.4-noarch.run file and I still get a "There was an md5sum mismatch with the kiosk base! Please run the wizard again." when downloading the base.

If I'm reading the file correctly, http://ponce.cc/porteus/i486/packages/k ... -kiosk.txt, the MD5 hash for the base ISO should be 00362aec47976e672c7b7055e4b99921. The porteus-kiosk-wizard-v2.0.4-noarch.run file however has an MD5 hash of MD5="fe9b9cbcec19ab8abc8b7a7c1860e529". I assume that hash is for the base ISO. I may try changing the wizard file to match what is posted on the website to see if it works.

Thank you for all you do!

User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Device not ready yet? Delaying x seconds.

Post#7 by Hamza » 05 Jun 2013, 14:49

I confirm that the correct md5sum is 00362aec47976e672c7b7055e4b99921 as written on our website.
NjVFQzY2Rg==

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Device not ready yet? Delaying x seconds.

Post#8 by fanthom » 05 Jun 2013, 16:39

@jmalon

wizard downloads following file:
http://ponce.cc/porteus/i486/packages/k ... -kiosk.txt
and pulls md5sums from there. you must have an old porteus-kiosk.txt in your /tmp folder so please delete it.

btw: in 3 hrs i'll update the wizard to always download new porteus-kiosk.txt instead of relaying on what's in /tmp.
that will be safer.
Please add [Solved] to your thread title if the solution was found.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#9 by jmalon » 05 Jun 2013, 18:34

I removed old porteus-kiosk.txt in my /tmp folder and it works now. Thank you!

FYI: The latest wizard has some yellow text in it. It is so bright, I can't make out what it says. My eyes are getting old though. Maybe it's just me.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#10 by jmalon » 05 Jun 2013, 19:32

I'm using the v2.0.4 wizard now. The ISO file boots fine in Virtualbox on my Dell GX280 but cannot get to the Internet (reported previously -- something in my environment). However, after making it a physical CD and trying to boot it in my Optiplex 755, I still get the message "Device not ready yet? Delaying x seconds. Error: Porteus data not found. Startup cannot continue." when booting with the new ISO. I've tried recreating and reburning the ISO with the same result." This CD boots fine in an IBM ThinkCentre (8090-22u) but cannot get to the Internet. I have been able to get to the Internet on previous PKE builds with this IBM.

So, I think two things are at play now.

1. Certain drivers may not be loaded in v.2.0.4 to allow it to boot properly. Here is the information for the OptiPlex 755 I'm using.

Code: Select all

lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 82Q35 Express PCI Express Root Port [8086:29b1] (rev 02)
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b3] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: mei
00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: ata_generic
00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02)
	Subsystem: Dell OptiPlex 755 [1028:0211]
	Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller [8086:2914] (rev 02)
	Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02)
	Subsystem: Dell Device [1028:0211]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
	Subsystem: Dell Optiplex 755 [1028:0211]

lsusb -t
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
2. I've got something wrong with my rootcopy setup that prevents PKE from getting through our proxy server. If you need to look at my iso here it is:
http://www.mediafire.com/download/k4kw1 ... chex-4.iso


I hope this is helpful. Thank you again!

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Device not ready yet? Delaying x seconds.

Post#11 by fanthom » 05 Jun 2013, 20:27

1. Certain drivers may not be loaded in v.2.0.4 to allow it to boot properly.
please follow debugging information from my previous post (mounting /dev/sr0 in /tmp/test)
I've got something wrong with my rootcopy setup that prevents PKE from getting through our proxy server.
you shouldn't keep prefs.js (containing your proxy details) in /rootcopy as it gets overridden by a one from 003-settings.xzm (this topic is covered by the Kiosk FAQ).
that's why you have no internet access. please update 003-settings.xzm with your prefs.js and all should be ok.
This CD boots fine in an IBM ThinkCentre (8090-22u) but cannot get to the Internet.
if this issue is different than prefs.js placed in /rootcopy then please post output of 'lspci -knn' from this machine.
Please add [Solved] to your thread title if the solution was found.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#12 by jmalon » 05 Jun 2013, 20:46

On the OptiPlex 755 booting from CD, after the "Device not ready yet?..." error I perform the following:

mkdir /tmp/test
mount /dev/sr0 /tmp/test
ls /tmp/test/porteus

I can see the porteus-kiosk-v2.0.4.sgn file.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Device not ready yet? Delaying x seconds.

Post#13 by fanthom » 05 Jun 2013, 21:07

ok - so now i'm confused as it should just work unless you did some weird modifications to initrd.xz.

is it the 'PKE-paychex-4.iso' which you are trying to boot on OptiPlex 755?
did you try to boot our default Kiosk 2.0.4 ISO on this PC?

next time when you get a failure please run 'mount' command and check if /dev/sr0 is mounted under /mnt/sr0 (you could also run 'ls /mnt/sr0/porteus' and check if sgn file is there)

thanks
Please add [Solved] to your thread title if the solution was found.

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#14 by jmalon » 05 Jun 2013, 21:39

1. is it the 'PKE-paychex-4.iso' which you are trying to boot on OptiPlex 755? -- Yes.

2. did you try to boot our default Kiosk 2.0.4 ISO on this PC? -- No, but will soon.

3. next time when you get a failure please run 'mount' command and check if /dev/sr0 is mounted under /mnt/sr0 (you could also run 'ls /mnt/sr0/porteus' and check if sgn file is there)

Just after the error message and issuing the mount command, I get the following:

rootfs on / type rootfs (rw)
proc on /proc type proc (rw, relatime)
sysfs on /sys type sysfs (rw, relatime)
none on /dev type devtmps (rw, relatime, size=1552192k, nr_inodes=219807, mode=255)

If I do a ls /mnt/sr0/porteus I get:
ls: /mnt/sr0/porteus: No such file or directory

If I do the mkdir /tmp/test, mount /dev/sr0 /tmp/test, ls /tmp/test/porteus is see the porteus-kiosk-v2.0.4.sgn file.

If I do a mount after that I see to following:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw, relatime)
sysfs on /sys type sysfs (rw, relatime)
none on /dev type devtmps (rw, relatime, size=1552192k, nr_inodes=219807, mode=255)
/dev/sr0 on /tmp/test type iso9660 (ro, relatime)

jmalon
Black ninja
Black ninja
Posts: 78
Joined: 21 Mar 2013, 19:39
Distribution: Linux Mint
Location: Collinsville, OK

Re: Device not ready yet? Delaying x seconds.

Post#15 by jmalon » 05 Jun 2013, 22:15

I put the proxy settings back into the 003-settings.xzm file and that fixes one issue.

Post Reply